Message281104
It seems to me that this is not documented. I'm even not sure that this change is compatible. Additional bit is saved only with protocol 4. The default protocol is 3, thus your should explicitly specify it. But protocol 4 is supported since 3.4. It seems to me that if you pickle the datetime object with the fold bit set with protocol 4, you could get invalid result when unpickle it in 3.4 and 3.5. Yet one doubtful detail is that the fold bit is added to the hour bit in datetime.time, but to the month field in datetime.datetime.
In any case __reduce_ex__ has the highest priority. After implementing it your can be sure that it would be used. |
|
Date |
User |
Action |
Args |
2016-11-18 12:04:13 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, belopolsky, yselivanov, Jeff Reback |
2016-11-18 12:04:13 | serhiy.storchaka | set | messageid: <1479470653.35.0.392676170557.issue28730@psf.upfronthosting.co.za> |
2016-11-18 12:04:13 | serhiy.storchaka | link | issue28730 messages |
2016-11-18 12:04:12 | serhiy.storchaka | create | |
|