Message186981
| Author |
ronaldoussoren |
| Recipients |
ezio.melotti, jfortier, mmilkin, ronaldoussoren, serhiy.storchaka |
| Date |
2013年04月15日.12:45:18 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1366029919.06.0.195027528593.issue17353@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I agree that plistlib shouldn't raise an exception for data that can represented as a valid plist file.
I've checked that the Cocoa class for generating plist files will happily create a plist file when the data is nested 100 levels deep. In that case NSData values generate lines of 12 characters long.
An unrelated issue: PlistWriter.writeValue should treat bytes instances the same as Data instances in Python 3. That would be a (small) feature enhencement, and hence can only be done for Python 3.4. |
|