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 bigfootjon
Recipients SilentGhost, bigfootjon, ronaldoussoren, serhiy.storchaka, slo.sleuth
Date 2018-03-13.17:29:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1520962160.84.0.467229070634.issue26707@psf.upfronthosting.co.za>
In-reply-to
Content
Support for KeyedArchives are not limited to the Swift implementation I linked to. They have been supported since Mac OS X since 10.2 (long before Swift came around). The documentation (https://developer.apple.com/documentation/foundation/nskeyedarchiver?language=objc) shows that NSKeyedArchive can only output in plist format since outputFormat is of type NSPropertyListFormat (allowing to output in either XML or binary).

The other unimplemented binary token types (URL, UUID, set, ordset) are not used under NSKeyedArchive (see the "Encoding Data and Objects" section of the documentation mentioned above) so there's no concern that supporting 0x80 (UID) will suddenly necessitate implementing the other unimplemented types. If you feel that it would be necessary to implement them in order to accept the patch I would be happy to try and implement them.

I know I certainly have an use case (reading to-do list data from the 2Do app) and the creator of this bug wanted to read SnapChat data files.

Currently, I am using a hot-patched plistlib._BinaryPlistParser to read the data I need (see attached for a snippet) and I would rather not do that, but if you think my use case scope does not warrant inclusion in the standard library then I'll just have to deal with that.
History
Date User Action Args
2018-03-13 17:29:20bigfootjonsetrecipients: + bigfootjon, ronaldoussoren, SilentGhost, serhiy.storchaka, slo.sleuth
2018-03-13 17:29:20bigfootjonsetmessageid: <1520962160.84.0.467229070634.issue26707@psf.upfronthosting.co.za>
2018-03-13 17:29:20bigfootjonlinkissue26707 messages
2018-03-13 17:29:20bigfootjoncreate