[issue36499] unpickling of a datetime object in 3.5 fails when pickled with 2.7

Josh Rosenberg added the comment: As noted, this is fixed in 3.6+. 3.5 is in security fix only mode ( https://devguide.python.org/#status-of-python-branches ), which is why the fix for #22005 wasn't backported. -- nosy: +josh.r resolution: -> duplicate stage: -> resolved status:

[issue36499] unpickling of a datetime object in 3.5 fails when pickled with 2.7

Karthikeyan Singaravelan added the comment: This seems to have been fixed with 8452ca15f41061c8a6297d7956df22ab476d4df4. I checked out your example locally and renamed pickle.py to another name to avoid module collision. Ran the below commands to pickle using Python 2 and to unpickle from

[issue36499] unpickling of a datetime object in 3.5 fails when pickled with 2.7

Change by Karthikeyan Singaravelan : -- nosy: +belopolsky, p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36499] unpickling of a datetime object in 3.5 fails when pickled with 2.7

New submission from Vadim : Unpickling fails when pickling is performed with 2.7 (pickledatetime.py) and unpickling is done with 3.5 (Tested on Ubuntu 16.04) Please see detailed error description and workaround in the comments to the attached files. -- components: Library (Lib)