Closed StefanKarpinski closed 10 years ago
This seems to not be a problem in the new package.
In [2]: using Dates
In [3]: sprint(io->serialize(io,date(2013,7,2)))
Out [3]: ERROR: date not defined
while loading In[3], in expression starting on line 1
in anonymous at In[3]:1
In [4]: sprint(io->serialize(io,Date(2013,7,2)))
Out [4]: "\x11\x01\x02\x04Date#\x14\x01\x02\x05Dates/\x7f\x11\x01\x02\tUTInstant#\x14\x01\x02\x05Dates\x14\x01\x11\0\x02\x03Day#\x14\x01\x02\x05Dates/\x7f\x11\x01\x02\x03Day#\x14\x01\x02\x05Dates/\x7f\x11\x01\x02\x05Int64#\x14\x01\x02\x04Core/K7\v\0\0\0\0\0"
Since the old Date{ISOCalendar}
is a bitstype, how do I make it serializable?
How rough is the transition from the old to the new package? I'm dealing with a codebase that uses Datetime
extensively and don't want to do anything super disruptive.
Probably not very disruptive (depending on what you're actually using). The main difference is date()
=> Date()
.
I'm happy to firedrill any questions/bugs if needed. You can get the new package by Pkg.clone("https://github.com/karbarcca/Dates.jl.git")
Did you give the new package a spin? I'd love to hear if you ran into any issues. I've mainly been adding a ton more tests over the last few weeks (enjoying finally getting around to using the code coverage tool). I feel like the core code is very stable these days. The main things on my agenda are ironing out some of the new Range issues, doing another pass over date parsing, and trying to tackle the "parameter" issue again (include Calendar/TimeZone as parameter? set them as globals?)