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 zeth
Recipients belopolsky, p-ganssle, zeth
Date 2019-08-28.05:36:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566970573.83.0.212597978405.issue37962@roundup.psfhosted.org>
In-reply-to
Content
Did you read the attached PR? For three lines longer, the method becomes more generally useful now.

As pointed out in the other thread that you pointed to, Javascript can parse Python's seralised datetime object but Python cannot parse Javascript's due to the fact that you don't want to.

That other thread points to a third thread that starts in 2012 so it seems that you really think that is a feature rather than a bug.

The name of the method is fromisoformat, not "parse our internal home made format". The line in the documentation seems a bit weird to me to be honest. It is saying that we could make it generally useful for you user but we don't want to.

The reply to this bug, "use the dateutil.parser.isoparse that I maintain instead" is beside the point, we are talking about the standard library one. Why not put that in the standard library then if it can actually parse iso 8601 format?
History
Date User Action Args
2019-08-28 05:36:13zethsetrecipients: + zeth, belopolsky, p-ganssle
2019-08-28 05:36:13zethsetmessageid: <1566970573.83.0.212597978405.issue37962@roundup.psfhosted.org>
2019-08-28 05:36:13zethlinkissue37962 messages
2019-08-28 05:36:13zethcreate