➜

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 belopolsky
Recipients alexandre.vassalotti, belopolsky, eddygeek, pitrou, serhiy.storchaka, tanzer@swing.co.at, tim.peters
Date 2015-10-12.18:19:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444673952.29.0.210553472394.issue22005@psf.upfronthosting.co.za>
In-reply-to
Content 
> The first issue can be solved by accepting str argument and encoding it to bytes.

A strong -1 from me.  Accepting bytes objects for year in 3.x (and str in 2.x) is a gross hack.  In the long run, I would like to see a public named constructor, e.g. datetime.datetime.load to be used in datetime pickles.

Can someone explain succinctly what the problem is?  Does it only affect pickles transferred between 2.x and 3.x Pythons?  If not, how can I reproduce the problem in 3.5?
History
Date User Action Args
2015-10-12 18:19:12belopolskysetrecipients: + belopolsky, tim.peters, pitrou, alexandre.vassalotti, serhiy.storchaka, eddygeek, tanzer@swing.co.at
2015-10-12 18:19:12belopolskysetmessageid: <1444673952.29.0.210553472394.issue22005@psf.upfronthosting.co.za>
2015-10-12 18:19:12belopolskylinkissue22005 messages
2015-10-12 18:19:12belopolskycreate