[issue1687] plistlib.py restricts to Python int when writing

Georg Brandl added the comment: Backported in r60098. -- nosy: +georg.brandl resolution: remind -> fixed status: pending -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1687] plistlib.py restricts to Python int when writing

lafcadio added the comment: tiran wrote: > Should it be backported to 2.5? I'm sure to understand what 'backport' means. Of course it would be nice if in future 2.5 versions the read data could be written. But for me its not important. __ Tracker <[EMAIL PROTECTE

[issue1687] plistlib.py restricts to Python int when writing

Changes by Christian Heimes: -- priority: -> normal resolution: fixed -> remind versions: -Python 2.6, Python 3.0 __ Tracker <[EMAIL PROTECTED]> __ __

[issue1687] plistlib.py restricts to Python int when writing

Christian Heimes added the comment: Fixed in trunk r59688 Should it be backported to 2.5? -- nosy: +tiran resolution: -> fixed status: open -> pending versions: +Python 2.6, Python 3.0 -Python 2.3, Python 2.4 __ Tracker <[EMAIL PROTECTED]>

[issue1687] plistlib.py restricts to Python int when writing

New submission from lafcadio: In PlistWriter.writeValue() the line "elif isinstance(value, int):" should be changed to "elif isinstance(value, int) or isinstance(value, long):" since in http://www.apple.com/DTDs/PropertyList-1.0.dtd is no limitation to signed 32-bit integer. It occured an e