Author hassanbot
Recipients belopolsky, bozo.kopic, ghaering, hassanbot, lemburg, serhiy.storchaka, xiang.zhang
Date 2020-09-17.21:51:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1600379480.3.0.943828726476.issue29099@roundup.psfhosted.org>
In-reply-to
Content
This still isn't fixed as of 3.8 (or in master I think).

I can understand why you wouldn't want to allow serializing and deserializing time zones, since tzinfo objects cannot be accurately serialized with a simple UTC offset, but you should at least get an error when trying to insert an aware object. Anything is better than it is now, where you get no warning or error when inserting the object, and get a hard to interpret error ("invalid literal for int() with base 10") when trying to retrieve it.

For deserialization, the datetime class now (since 3.7) includes a fromisoformat() method that could be used as a counterpart to the isoformat() method used when serializing. At least it would be consistent then.
History
Date User Action Args
2020-09-17 21:51:20hassanbotsetrecipients: + hassanbot, lemburg, ghaering, belopolsky, serhiy.storchaka, xiang.zhang, bozo.kopic
2020-09-17 21:51:20hassanbotsetmessageid: <1600379480.3.0.943828726476.issue29099@roundup.psfhosted.org>
2020-09-17 21:51:20hassanbotlinkissue29099 messages
2020-09-17 21:51:20hassanbotcreate