|
From: Mark B. <ma...@gm...> - 2013-09-30 13:45:45
|
The design of the function datestr2num, unfortunately, has an undesired
side-effect.
Today (September 30) I cannot convert monthly data, as February doesn't
have 30 days.
Conversion of:
datestr2num('2000-02')
Gives an error:
ValueError: day is out of range for month
Should I file a bug report or a feature request?
Thanks,
Mark
>
> On Thu, Sep 19, 2013 at 11:38 PM, Goyo <goy...@gm...> wrote:
>
>> 2013/9/19 Mark Bakker <ma...@gm...>:
>> > Hello List,
>> >
>> > When I use datestr2num('2010-05') it nicely converts that to a number
>> > representing the date.
>> > When I convert that number back with num2date, it turns out it sets the
>> day
>> > to the 19th of the month. The dime is 0:00:00.
>> > Any reason it is set to the 19th instead of the first?
>> > Maybe because today it the 19th, or is that just a coincidence?
>>
>> datestr2num calls dateutil.parser.parse, which by default uses the
>> current date at 00:00:00 for missing fields. The dateutil function
>> also can use a "default" argument to change this bahavoir but it is
>> not available in datestr2num.
>>
>>
>> http://labix.org/python-dateutil#head-a23e8ae0a661d77b89dfb3476f85b26f0b30349c
>>
>> Goyo
>>
>
>
|