Open sscherfke opened 2 years ago
Hi! You're right, it only parses UTC. See the call to the Rust library: https://github.com/gukoff/dtparse/blob/master/src/lib.rs#L20
We could make parsing timezone-aware. I think fixed offsets should be easy to support.
It's harder to support real-world timezones (PST, EST, Europe/Berlin, etc), as their definitions change over the time, and one must think how to bring chrono-tz and pytz together.
Is your usecase strictly fixed offsets?
Fixed offsets would be a huge benefit and cover most use cases. :)
I am not able to parse timezones other an
Z
/+00:00
with dtparse 1.3.2.I'd also expect that tzinfo is attached to the datetime for
Z
/+00:00
:Did I miss something or is this a bug or even expected behavior?