confusing deprecation notice for `chrono::TimeZone::datetime_from_str` about chrono

[pitdicker]

You probably want to parse the input as a NaiveDateTime. That is the closest type to your input, because the timezone information ('UTC') is not part of the input but something you add to it. Code:

NaiveDateTime::parse_from_str(foo, "%Y-%m-%d %H:%M").unwrap().and_utc();

[pitdicker]

It does since 0.4.32, released two days ago (see #1342) 😄.

[jtmoon79]

convert a Datetime<FixedOffset> to a Datetime<Utc>

Can you use the From trait?

    let dtfo: DateTime<FixedOffset> = DateTime::parse_from_str("19700102T23:55:55+00", "%Y%m%dT%H:%M:%S%#z").unwrap();
    let dtutc: DateTime<Utc> = DateTime::<Utc>::from(dtfo);

[decathorpe]

hum ... from the docs for DateTime::parse_from_str:

Note that this method requires a timezone in the input string.

My input string does not have a timezone, but I know that it's a UTC timestamp.

So should I use a NaiveDateTime? But From<NaiveDateTime> is not implemented for DateTime<Utc>.

[decathorpe]

Indeed, using Datetime::parse_from_str is not possible with the format I have, I get: "input is not enough for unique date and time"

[decathorpe]

Yup, this works, thank you!

Maybe the deprecation warning could mention both DateTime::parse_from_str and NaiveDateTime::parse_from_str then? It looks like the former is only a replacement if the format has specified a timezone, and the latter needs to be used if the timezone is not part of the format.

[decathorpe]

Ah! Thank you. I probably did not notice because 0.4.32 failed to build on docs.rs.