Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #102892

Re: problem with dateutil

Show all headers | View raw

On 13/02/2016 17:58, Tom P wrote:
> I am writing a program that has to deal with various date/time formats
> and convert these into timestamps. It looks as if dateutil.parser.parse
> should be able to handle about any format, but what I get is:
>
> datetimestr = '2012-10-22 11:22:33'
> print(dateutil.parser.parse(datetimestr))
> result: datetime.datetime(2012, 10, 22, 11, 22, 33)
>
> However:
> datetimestr = '2012:10:22 11:22:33'
> print(dateutil.parser.parse(datetimestr))
> result: datetime.datetime(2016, 2, 13, 11, 22, 33)
>
> In other words, it's getting the date wrong when colons are used to
> separate YYYY:MM:DD. Is there a way to include this as a valid format?
>

 From 
http://labix.org/python-dateutil#head-a23e8ae0a661d77b89dfb3476f85b26f0b30349c

<quote>
parserinfo
     This parameter allows one to change how the string is parsed, by 
using a different parserinfo class instance. Using it you may, for 
example, intenationalize the parser strings, or make it ignore 
additional words.
</quote>

HTH.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

problem with dateutil Tom P <werotizy@freent.dd> - 2016-02-13 18:58 +0100
  Re: problem with dateutil Gary Herron <gherron@digipen.edu> - 2016-02-13 10:13 -0800
    Re: problem with dateutil Tom P <werotizy@freent.dd> - 2016-02-13 21:27 +0100
      Re: problem with dateutil Gary Herron <gherron@digipen.edu> - 2016-02-13 12:45 -0800
        Re: problem with dateutil Tom P <werotizy@freent.dd> - 2016-02-14 13:26 +0100
  Re: problem with dateutil Mark Lawrence <breamoreboy@yahoo.co.uk> - 2016-02-13 21:01 +0000
    Re: problem with dateutil Tom P <werotizy@freent.dd> - 2016-02-14 13:27 +0100

csiph-web