Closed KristofferC closed 3 years ago
Currently TimeZones.jl uses serialization to store time zones with pre-computed transitions. As Julia and TimeZones have improved performance over time I'm hoping to switch over to calculating these transitions on the fly which would remove any reliance on serialization and thus avoid this problem.
If it turns out that this approach is too slow we should be able to store this information on disk using alternative storage methods like a custom format or another serialization format.
If we have to keep storing it with serialization can we at least do something like including the julia version in the file path.
This is super-annoying
If we have to keep storing it with serialization can we at least do something like including the julia version in the file path.
I will do this today.
Interestingly this no longer reproduced for tz"UTC"
I guess because we now special case that in the parser to be faster.
But does fail as expected for tz"America/Winnipeg"
Fixed in TimeZones 1.5.3
Because I happened to install TimeZones on julia master first.