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 serhiy.storchaka
Recipients alexandre.vassalotti, pitrou, serhiy.storchaka
Date 2012-11-15.22:17:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353017836.41.0.616835279118.issue12848@psf.upfronthosting.co.za>
In-reply-to
Content
The C implementation writes and reads BINBYTES and BINUNICODE up to 4G (on 64-bit platform). The Python implementation writes and reads BINBYTES and BINUNICODE up to 2G. What should be compatible fix? Allow the Python implementation to write and read up to 4G? Then Python can pickle a large data which can't be unpickled on non-patched Python (and on 2.7). Limit size to 2G? Then non-patched Python (including 3.1) can pickle a data which can't be unpickled on patched Python.

Also there is an unpleasant fact that 64-bit Python can pickle data which can't unpickle 32-bit Python.
History
Date User Action Args
2012-11-15 22:17:16serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, alexandre.vassalotti
2012-11-15 22:17:16serhiy.storchakasetmessageid: <1353017836.41.0.616835279118.issue12848@psf.upfronthosting.co.za>
2012-11-15 22:17:16serhiy.storchakalinkissue12848 messages
2012-11-15 22:17:16serhiy.storchakacreate
Morty Proxy This is a proxified and sanitized view of the page, visit original site.