[issue22993] Plistlib fails on certain valid plist values

Serhiy Storchaka added the comment: An issue with out of range timestamps was resolved in issue26709. -- ___ Python tracker ___ ___ Py

[issue22993] Plistlib fails on certain valid plist values

Serhiy Storchaka added the comment: Related issue is issue10733. Not all plists produced by Apple's tools can be proceeded by plistlib. -- ___ Python tracker ___ ___

[issue22993] Plistlib fails on certain valid plist values

Serhiy Storchaka added the comment: Another limitation is that on 32-bit platform it is impossible to load date before datetime.datetime(1901, 12, 13, 20, 45, 52) from binary plist. >>> plistlib.loads(b'bplist003'+struct.pack('>d', -2**31 - (31 * 365 + 8) * >>> 86400)+b'\x08\x00\x00\x00\x00\x0

[issue22993] Plistlib fails on certain valid plist values

Ned Deily added the comment: (Currently, it is not possible to edit a particular message in an issue. You could add a replacement comment to the issue and ask that the older message be delete.) This seems to be a problem date. As documented, plistlib converts plist dates to/from Python datet

[issue22993] Plistlib fails on certain valid plist values

Connor Wolf added the comment: Aaaand there is no markup processing. How do I edit my report? -- ___ Python tracker ___ ___ Python-bug

[issue22993] Plistlib fails on certain valid plist values

New submission from Connor Wolf: I'm using plistlib to process plist files produced by an iphone app. Somehow, the application is generating plist files with a absolute date value along the lines of `-12-30T00:00:00Z`. This is a valid date, and the apple plist libraries can handle this wit