Curtis Vogt
Curtis Vogt
Kick starting CI
@NHDaly sorry for not giving this the attention it deserves. Been swamped lately. I'll try to be faster on additional reviews
Related to: https://github.com/JuliaTime/TimeZones.jl/issues/300
Note that you only really observe this issue with the "etcetera" tz source file.
Unfortunately this needs to be handled on a case-by-case basis as time zone abbreviations are not guaranteed to be unique. What should be done however is allowing end users to...
It's definite possible to get it to parse the output. Unfortunately the output only shows the UTC offset for that specific timestamp which means that parsing it will result a...
The DateFormat specification could use a re-think. It would be nice if when parsing you could state a section was optional. Something like `df"yyyy-mm-dd HH:MM:SS(.sss)zzz"`. Additionally, I dislike that I'm...
Mostly the optional specifiers for parsing would be useful.
@rofinn just ran into this one: ```julia julia> ZonedDateTime("2017-01-28T11:59:59+00:00") ERROR: ArgumentError: Unable to parse date time. Expected directive Delim(.) at char 20 ```
Something related would be to make sure that `repr` for `ZonedDateTime` print as parsable Julia code `ZonedDateTime(2018, 11, 2, 12, 55, tz"America/Winnipeg")` and have `print` display the current compact representation...