Re: [julia-users] Re: Call for Date/DateTime strings to parse

2014-05-29 Thread Jacob Quinn
Thanks for all the suggestions everyone! I'm feeling good about the core IO upgrade and the flexibility it provides. I really think that this parsing/formatting functionality, coupled with how easy it already is to format things in Julia (@sprintf, interpolation, etc.), a user should be able to

[julia-users] Re: Call for Date/DateTime strings to parse

2014-05-28 Thread Keith Campbell
The python dateutil .parse() function has a fairly extensive set of tests at http://bazaar.launchpad.net/~dateutil/dateutil/trunk/view/head:/test.py The license is at: http://bazaar.launchpad.net/~dateutil/dateutil/trunk/view/head:/LICENSE Keith On Wednesday, May 28, 2014 10:38:11 AM UTC-4,

[julia-users] Re: Call for Date/DateTime strings to parse

2014-05-28 Thread Tony Fong
I have seen * ddmmmyy (01Dec09) * ddmmm (01Dec2009) * single digit month code stemming from futures delivery codes i.e. F4 (Jan2014), so 1F4 for very terse near-term date. http://www.cmegroup.com/market-data/volume-open-interest/volume-by-price-faq.html#q7 On Wednesday, May 28, 2014

[julia-users] Re: Call for Date/DateTime strings to parse

2014-05-28 Thread Matt Bauman
I know there are a gazillion different ways to specify the timezone, but one I see commonly that isn't covered to my knowledge is `X` from ISO 8601. E.g., how you print Dates in zulu time: 2014-05-28T16:46:04Z. I'm very much looking forward to the new Dates.jl. Thanks Jacob! On Wednesday,