➜

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 JelleZijlstra, alexandre.vassalotti, pitrou, serhiy.storchaka
Date 2016-06-26.21:59:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466978399.56.0.39385482636.issue22890@psf.upfronthosting.co.za>
In-reply-to
Content 
There is the _compat_pickle module that purposed to support backward and forward compatibility for renamed or moved classes and modules.

StringIO.StringIO in 2.x corresponds to io.StringIO or io.BytesIO. The problem is that we can't determine what of classes is a match in every concrete case, especially if StringIO.StringIO is empty.

But since cStringIO.StringIO is not pickleable either, I now think that it is not worth to support to support compatibility with pickled StringIO.StringIO instances.
History
Date User Action Args
2016-06-26 21:59:59serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, alexandre.vassalotti, JelleZijlstra
2016-06-26 21:59:59serhiy.storchakasetmessageid: <1466978399.56.0.39385482636.issue22890@psf.upfronthosting.co.za>
2016-06-26 21:59:59serhiy.storchakalinkissue22890 messages
2016-06-26 21:59:59serhiy.storchakacreate