This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author p-ganssle
Recipients alex.gronholm, ammar2, belopolsky, brett.cannon, dlenski, godlygeek, hongweipeng, jwilk, mehaase, p-ganssle, rdb
Date 2022-02-02.17:32:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643823147.48.0.89346472828.issue35829@roundup.psfhosted.org>
In-reply-to
Content
I don't think it's necessary to add a feature to `isoformat()` just for the purpose of being able to add the corresponding parser, particularly when the plan is to implement a much broader ISO 8601 parser for Python 3.11 (I've done most of the implementation in C already, I can share the progress I've made, particularly if someone else wants to pick up the baton there before I get back to it).

That said, I think it's useful for `isoformat()` to be able to output UTC times as "Z", so we may as well do that as part of 3.11 anyway. I think that's a separate issue to discuss, so I've created bpo-46614 to hammer out the details.
History
Date User Action Args
2022-02-02 17:32:27p-gansslesetrecipients: + p-ganssle, brett.cannon, belopolsky, jwilk, alex.gronholm, dlenski, rdb, ammar2, mehaase, hongweipeng, godlygeek
2022-02-02 17:32:27p-gansslesetmessageid: <1643823147.48.0.89346472828.issue35829@roundup.psfhosted.org>
2022-02-02 17:32:27p-gansslelinkissue35829 messages
2022-02-02 17:32:27p-gansslecreate