[Python-Dev] iso8601 parsing

Chris Barker chris.barker at noaa.gov
Fri Dec 1 12:47:30 EST 2017

On Wed, Nov 29, 2017 at 4:19 PM, Paul G <paul at ganssle.io> wrote:

> I can write at least a pure Python implementation in the next few days, if
> not a full C implementation. Shouldn't be too hard since I've got a few
> different Cython implementations sitting around anyway.


> On November 29, 2017 7:06:58 PM EST, Alexander Belopolsky <
> alexander.belopolsky at gmail.com> wrote:
>> On Wed, Nov 29, 2017 at 6:42 PM, Chris Barker <chris.barker at noaa.gov>
>> wrote:
>>> indeed what is the holdup? I don't recall anyone saying it was a bad
>>> idea in the last discussion.
>>> Do we just need an implementation?
>>> Is the one in the Bug Report not up to snuff? If not, then what's wrong
>>> with it? This is just not that hard a problem to solve.
>> See my comment from over a year ago: <https://bugs.python.org/
>> issue15873#msg273609>.  The proposed patch did not have a C
>> implementation, but we can use the same approach as with strptime and call
>> Python code from C.  If users will start complaining about performance, we
>> can speed it up in later releases.  Also the new method needs to be
>> documented.  Overall, it does not seem to require more than an hour of work
>> from a motivated developer, but the people who contributed to the issue in
>> the past seem to have lost their interest.


Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171201/4a005d81/attachment.html>

More information about the Python-Dev mailing list