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 Michael Crouch, alexandre.vassalotti, docs@python, pitrou, serhiy.storchaka, sschwarzer
Date 2015-10-28.17:10:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446052204.45.0.960571450426.issue21333@psf.upfronthosting.co.za>
In-reply-to
Content
PicklingError is raised in following cases:

1. Programmical Pickler error (Pickler.__init__() was not called by subclass' __init__()).

2. Due to protocol or implementation limitations: memoizing more than 2**32 objects, saving non-ASCII globals with protocol < 3, etc. Exception type is implementation depended. Sometimes OverflowError or struct.error can be raised instead.

3. When __reduce__/__reduce_ex__ returns invalid value: neither str or tuple, a tuple has wrong size, first tuple element is not a callable, first argument for __newobj__/__newobj_ex__ has no __new__ or doesn't match a type of pickled object, global lookup is failed or doesn't match pickled object, etc.

4. When extension code is not an integer or out of range.
History
Date User Action Args
2015-10-28 17:10:04serhiy.storchakasetrecipients: + serhiy.storchaka, sschwarzer, pitrou, alexandre.vassalotti, docs@python, Michael Crouch
2015-10-28 17:10:04serhiy.storchakasetmessageid: <1446052204.45.0.960571450426.issue21333@psf.upfronthosting.co.za>
2015-10-28 17:10:04serhiy.storchakalinkissue21333 messages
2015-10-28 17:10:04serhiy.storchakacreate