[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by Alexander Belopolsky : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: New changeset 0e06be836ca0d578cf9fc0c68979eb682c00f89c by Alexander Belopolsky (Miss Islington (bot)) in branch '3.7': Add What's new entry for datetime.fromisoformat (GH-5559) (GH-5939)

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by miss-islington : -- pull_requests: +5709 ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: New changeset 22864bc8e4a076bbac748ccda6c27f1ec41b53e7 by Alexander Belopolsky (Paul Ganssle) in branch 'master': Add What's new entry for datetime.fromisoformat (#5559)

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by Paul Ganssle : -- pull_requests: +5380, 5381 ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by Paul Ganssle : -- pull_requests: +5380 ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

R. David Murray added the comment: Correct, a new feature should always get a what's new entry. You could submit a PR for it :) -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: maybe it's worth adding an entry in python 3.7 "what's new" ? I think it was a very long awaited issue. The opposite of isoformat() is a very frequent question from python newcomers -- ___ Python

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: New changeset 09dc2f508c8513e0466a759cc27a09108c1e55c2 by Alexander Belopolsky (Paul Ganssle) in branch 'master': bpo-15873: Implement [date][time].fromisoformat (#4699)

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Daniel Holmes added the comment: I wanted to note here... I've been trying to get strptime to work with the types of dates specified in this request and came across a documentation bug here: https://docs.python.org/3.5/library/time.html#time.strptime You can see that the

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Paul Ganssle added the comment: > Not if the time is associated with a particular day. Imagine implementing > datetime.fromisoformat by separately calling date.fromisoformat and > time.fromisoformat. The date will be off by one day if you naively rounded > 2017-12-18

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: Not if the time is associated with a particular day. Imagine implementing datetime.fromisoformat by separately calling date.fromisoformat and time.fromisoformat. The date will be off by one day if you naively rounded 2017-12-18 23:59

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Paul Ganssle added the comment: @martin.panter I don't see the problem here? Wouldn't 23:59.995 round up to 00:00? -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: Regarding Matthieu’s RFC 3339 parser, Victor wanted to use the round-half-to-even rule to get a whole number of microseconds. But considering the “time” class cannot represent 24:00, how do you round up in the extreme case past 23:59?

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: I finally released my work. It looks like Paul's work is more comprehensive, but if you want to pick one thing or two in mine, feel free. -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by Roundup Robot : -- pull_requests: +4729 ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Paul Ganssle added the comment: > The other difference is Mattieu guarantees ValueError for invalid input > strings, which I think is good. I forgot to address this - but I don't think this is a difference in approaches. If you pass `None` or an int or something, the

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: +1 on what Paul said. Mathieu, the goal for 3.7 will be to get Paul's PR merged. It will be great if you could help in reviewing it. We can return to the features in your PR during the 3.8 development cycle.

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Paul Ganssle added the comment: > The better is the enemy of the good here. Given the history of this issue, I > would rather accept a well documented restrictive parser than wait for a more > general code to be written. Note that we can always relax the parsing rules

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: I'm right now available again to work on this issue. I'll submit a pull request within a week with all issues addressed Le 4 déc. 2017 11:45 PM, "Alexander Belopolsky" a écrit : > > Alexander Belopolsky

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: The better is the enemy of the good here. Given the history of this issue, I would rather accept a well documented restrictive parser than wait for a more general code to be written. Note that we can always relax the

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: The other difference is Mattieu guarantees ValueError for invalid input strings, which I think is good. -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: P-ganssle seems to be proposing to limit parsing to exactly what “datetime.isoformat” produces; i.e. whole number of seconds, milliseconds or microseconds. Personally I would prefer it without this limitation, like in Mathieu’s patches.

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by Paul Ganssle : -- pull_requests: +4611 ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Elvis Pranskevichus added the comment: I think that both the pyiso8601 and boxed/iso8601 implementations parse ISO 8601 strings incorrectly. The standard explicitly says that all truncated datetime strings are *reduced accuracy timestamps*. In other words, "2017-10" is

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Anders Hovmöller added the comment: @larsonreever That lib is pretty limited, in that it doesn't handle dates or deltas. Again: my lib that is linked above does and has comprehensive tests. -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

larsonreever added the comment: Otherwise, py8601 (https://bitbucket.org/micktwomey/pyiso8601/) looks pretty popular and well maintained (various committers, started in 2012, last commit in 2016). I don't think that we should add the iso8601 module to the stdlib, but merge iso8601 "features"

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Mantas Zimnickas : -- nosy: +Mantas Zimnickas ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Alexander Belopolsky : -- versions: +Python 3.7 -Python 3.6 ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Cherniavsky Beni : -- nosy: +cben ___ Python tracker ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: Please move _parse_isotime to _strptime so that it can be called from C implementation. Also, the new method should be documented. -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: updated version with SilentGhost's concerns addressed. -- Added file: http://bugs.python.org/file44019/fromisoformat_regexinclasses2.patch ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Mathieu Dupuy : Added file: http://bugs.python.org/file44016/fromisoformat_strptimesingledispatch.patch ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Mathieu Dupuy : Added file: http://bugs.python.org/file44015/fromisoformat_regexinclasses.patch ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: I'm back on the issue. I'm currently stuck on the design. We need to store the regexes somewhere, and that's what causes problem : I can't really find a good place to store them. We basically have two possible designs : * single dispatch kind, class-type

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: Mathieu: Maybe you haven’t seen some of the comments on your older patches. E.g. my comment on fromisoformat4.patch about improper use of “with self.assertRaises(...)” still stands. Also, adding some documentation to the patch might help the likes of Anders

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Anders Hovmöller added the comment: Hmm, ok. I guess I was confused by "dates and times" part of the subject. Ok, so only datetimes. My other comments still apply though. > On 19 Jul 2016, at 16:20, Mathieu Dupuy wrote: > > > Mathieu Dupuy added the comment: > >

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: because it limits itself to only support the RFC 3339 subset, as explained in the begining of the discussion. 2016-07-19 16:07 GMT+02:00 Anders Hovmöller : > > Anders Hovmöller added the comment: > > The tests attached to this ticket seem

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Anders Hovmöller added the comment: The tests attached to this ticket seem pretty bare. Issues that I can spot directly: - only tests for datetimes, not times or dates - only tests for zulu and "-8:00” timezones - no tests for invalid input (parsing a valid date as a datetime for example) -

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: I would very much like to see this ready before the feature cut-off for Python 3.6. Could someone post a summary on python-ideas to get a show of hands on some of the remaining wrinkles? I would not worry about a C implementation at this point. We can

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Alexander Belopolsky : -- nosy: -Alexander.Belopolsky ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Anders Hovmöller added the comment: > > By the way, I just discovered, that the way we treat microseconds differs > from the strptime one : we are smarter read every digits and smartly round to > six, strptime doesn't go that far and just *truncate* to this. Should go that > way, for

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: Hi. I'm back, and willing to move forward on this issue. With the new code layout, the compiled regexes now lay in datetime classes as class attributes. Will it be possible to import date, time and datetime from datetime.py in _datetime.c without a problem ?

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Eric Hanchrow : -- nosy: +Eric.Hanchrow ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: If you decide to only do a Python implementation, the main reason to write a wrapper in C would be because the datetime class is defined in C. Similar to how the datetime_strptime() function in Modules/_datetimemodule.c imports and calls

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: I know. Martin was suggesting to defer the processing to an actual Python implementation, hence my answer. -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

STINNER Victor added the comment: > If I defer the actual processing to the Python part, what's the point of > doing a C part ? Currently, the "datetime" module is fully implemented in C, it's the _datetime module in practice (accessed by the datetime module namespace). --

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: What I really want is to use regex in the C part as I did for the python one. It's the best approach and by very far. I need to figure out how to use regex in CPython internals. If I defer the actual processing to the Python part, what's the point of doing a C

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: Did you see my class attributes suggestion a couple messages back? That might solve your dispatch problem: def _parse_isodatetime(cls, string): match = cls._iso_regex.match(...) class time: _iso_regex = re.compile(...) # or time._iso_regex =

[issue15873] datetime: add ability to parse RFC 3339 dates and times

SilentGhost added the comment: Probably only other solution that I see is to add the third argument, an actual class, e.g.: _parse_isodatetime(cls, string, datetime) -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: crap, here is the attachment. Yeah, but I really would like to use regex in the C version (unless you strongly disadvise), so we will have the same logic and the same problem. And I never made a patch for the C interpreter itself, so the C equivalent is not

[issue15873] datetime: add ability to parse RFC 3339 dates and times

SilentGhost added the comment: Mathieu, nothing was attached. The penalty's worth only a few if statements, I wouldn't worry too much about it. Besides, a C version is going to be provided as well, right? Perhaps the following approach might solve the subclasses problem: regex =

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Aymeric Augustin added the comment: martin.panter: of course, I'm fine with integrating that code into Python. deronnax: could you create a ticket on https://code.djangoproject.com/ highlighting the differences between Django's original implementation and the improved version that you worked

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: SilentGhost: the dictionary single dispatch thing attached (apply on top of the last, fromisoformat_new3). I mind the performance penalty for date-only parsing users, but the code is definitively shorter and more elegant. But we have a major problem: tests

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: New patch with all your concerns addressed (martin.panther+ silentghost) EXCEPT the single dispatch dictionary thing. -- Added file: http://bugs.python.org/file41945/fromisoformat_new3.patch ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by SilentGhost : -- nosy: +SilentGhost ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: Hi Aymeric Augustin. I am guessing you are the original author of the code and tests in Django for parsing datetime strings (https://bugs.python.org/issue15873#msg260342). If so, would you be happy for it to be incorporated into Python? Mathieu: I left a

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: Crap, I just checked spams today and almost all mails of the reviewboard landed in spams ! So I made a new patch addressing all concerns: * regex moved closer to where they're used * regex globals start with an _ * case insensitive regex + handling(already

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: OK, I know I post a lot, but this one should be the good one: * recoded from scratch. Apart the algorithm, nothing come from Django anymore. * help me fill the docstring, I'm not inspired * datetime has few tests since it use the implementation of

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: (OK, I said a stupidity: datetime's strptime handle microseconds. But time's one doesn't) -- ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: simpler version using a simpler, stricter regex -- Added file: http://bugs.python.org/file41934/simplerfromisoformat.patch ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: Oh my god you're right. Thanks there is the re.ASCII flag. 2016-02-16 15:07 GMT+10:30 Martin Panter : > > Martin Panter added the comment: > > The regular expression r"\d" matches any digit in Unicode I think, not > just ASCII digits

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: The regular expression r"\d" matches any digit in Unicode I think, not just ASCII digits 0-9. Perhaps we should limit it to ASCII digits. Or is it intended to allow non-ASCII digits like in "२०१६-०२-१६ ०१:२१:१४"? --

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: The real question is : should we accept whatever iso8601 format is common to be found on the internet, or just be able to consume back the string issued by isoformat. From that results the answers to the questions you're asking: don't accept single digits,

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: It looks to me like you copied a lot of code, doc strings, tests, etc from and . I wouldn’t call it trivial. There is a BSD

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: > I suggest to parse directly the string with C code, since the format looks > quite simple (numbers and a few separators). But some of them are optional. And I would really like to mimic the same implementation logic in C. Now I think the python version is

[issue15873] datetime: add ability to parse RFC 3339 dates and times

STINNER Victor added the comment: > No regex available at all in CPython? It's not really convenient to use the re module in C. > Otherwise, yeah, if I have to, I can do it with strptime. I suggest to parse directly the string with C code, since the format looks quite simple (numbers and a

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: > Hum, you should use the same rounding method than datetime.datetime.fromtimestamp(): ROUND_HALF_UP, as round(). In practice, you can for example pass a floating point number as microseconds to datetime.datetime constructor. Unfortunately, you're mistaking with

[issue15873] datetime: add ability to parse RFC 3339 dates and times

STINNER Victor added the comment: > How does it parse this date: > 2016-02-15T11:59:46.16588638674+09:00 Mathieu Dupuy added the comment: > discarding the microseconds digits after the 6th. Hum, you should use the same rounding method than datetime.datetime.fromtimestamp(): ROUND_HALF_UP, as

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: slightly improved + addresses issues stated here : https://bugs.python.org/review/15873/diff/16581/Lib/datetime.py#newcode1418Lib/datetime.py:1418 -- Added file: http://bugs.python.org/file41926/fromisoformat3.patch

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: discarding the microseconds digits after the 6th. 2016-02-15 13:30 GMT+10:30 karl : > > karl added the comment: > > About > > > Actually, I realized that the best implementation of parsing rfc 3339 > > is in django dateparse utils. To me

[issue15873] datetime: add ability to parse RFC 3339 dates and times

karl added the comment: About > Actually, I realized that the best implementation of parsing rfc 3339 > is in django dateparse utils. To me it's the finest, the most > elegant, and no other one can claim to be more robust since it's > probably the #1 iso parsing functions used in python.

[issue15873] datetime: add ability to parse RFC 3339 dates and times

karl added the comment: >From https://www.djangoproject.com/foundation/cla/faq/ > Am I giving away the copyright to my contributions? > > No. This is a pure license agreement, not a copyright assignment. You > still maintain the full copyright for your contributions. You are > only providing

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: I don't know. The taken code is really little, modified, and is nothing much that an implementation you had seen a while ago, and recoded by memory not remembering where you saw it in the first place. Do you think that's really an issue ? --

[issue15873] datetime: add ability to parse RFC 3339 dates and times

STINNER Victor added the comment: Is the django license compatible with the Python license? -- ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: (slightly improved version, better use of timedelta) -- Added file: http://bugs.python.org/file41923/fromisoformat2.patch ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: Here is the PoC with code taken from django.utils.parse_datetime and adapted for the datetime module (I didn't ask for their agreement yet). Of course tests pass. For me it's the most elegant solution. (I think date and time also need their "fromisotimestamp"

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: #12006 will unfortunately of no use for this one. Actually, I realized that the best implementation of parsing rfc 3339 is in django dateparse utils. To me it's the finest, the most elegant, and no other one can claim to be more robust since it's probably the

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Jakub Stasiak : -- nosy: +jstasiak ___ Python tracker ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

STINNER Victor added the comment: I'm working on the OpenStack project and iso8601 is heavily used. > Otherwise, py8601 (https://bitbucket.org/micktwomey/pyiso8601/) looks pretty > popular and well maintained (various committers, started in 2012, last commit > in 2016). I don't think that

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: So, shall we include it ? Otherwise, py8601 (https://bitbucket.org/micktwomey/pyiso8601/) looks pretty popular and well maintained (various committers, started in 2012, last commit in 2016). I think we should hurry, that's a great shame it has been while Python

[issue15873] datetime: add ability to parse RFC 3339 dates and times

STINNER Victor added the comment: See also #12006 for ISO 8601: "The datetime.strftime() and date.strftime() methods now support ISO 8601 date directives %G, %u and %V. (Contributed by Ashley Anderson in issue 12006.)". -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Mihai Capotă : -- nosy: +mihaic ___ Python tracker ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Piotr Dobrogost : -- nosy: +piotr.dobrogost ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Alexander Belopolsky : -- versions: +Python 3.6 -Python 3.4 ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Ethan Furman et...@stoneleaf.us: -- nosy: -ethan.furman ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Paul Bryan pbr...@anode.ca: -- nosy: +pbryan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list mailing list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

karl added the comment: After inspections, the best library for parsing RFC3339 style date is definitely: https://github.com/tonyg/python-rfc3339/ Main code at https://github.com/tonyg/python-rfc3339/blob/master/rfc3339.py -- ___ Python tracker

[issue15873] datetime: add ability to parse RFC 3339 dates and times

karl added the comment: I had the issue today. I needed to parse a date with the following format. 2014-04-04T23:59:00+09:00 and could not with strptime. I see a discussion in March 2014 http://code.activestate.com/lists/python-ideas/26883/ but no followup. For references:

[issue15873] datetime: add ability to parse RFC 3339 dates and times

karl added the comment: On closer inspection, Anders Hovmöller proposal doesn't work. https://github.com/boxed/iso8601 At least for the microseconds part. In http://tools.ietf.org/html/rfc3339#section-5.6, the microsecond part is defined as: time-secfrac= . 1*DIGIT In

[issue15873] datetime: add ability to parse RFC 3339 dates and times

karl added the comment: Noticed some people doing the same thing https://github.com/tonyg/python-rfc3339 http://home.blarg.net/~steveha/pyfeed.html https://wiki.python.org/moin/WorkingWithTime -- ___ Python tracker rep...@bugs.python.org

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Iakov Davydov da...@myths.ru: -- nosy: +davydov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list mailing

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Ethan Furman et...@stoneleaf.us: -- nosy: +ethan.furman ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Berker Peksag berker.pek...@gmail.com: -- nosy: +berker.peksag ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +perey ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list mailing

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Éric Araujo added the comment: John listed four modules with issues in the first message, and now we have proposals for two more modules. Could you work together to make a unified patch? Alexander, do you think there is a need to check python-ideas or python-dev before working on this? (I

  1   2   >