➜

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 canjobear
Recipients canjobear, serhiy.storchaka
Date 2016-03-09.20:10:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457554203.88.0.0908332368522.issue26522@psf.upfronthosting.co.za>
In-reply-to
Content 
Ah, I get the same result as you in a clean interpreter session. Looks like it's not Python's fault.

The bug seems to arise from an interaction with cloudpickle 0.2.1 (and only in IPython), which puts the bad value into a cache somewhere in the pickle module.

So I'll take this issue to cloudpickle. 



In [1]: import cloudpickle

In [2]: cloudpickle.dumps(object.__new__)
Out[2]: '\x80\x02cemail.MIMEAudio\n__new__\nq\x00.'

In [3]: import pickle

In [4]: pickle.whichmodule(object.__new__, None)
Out[4]: 'email.MIMEAudio'
History
Date User Action Args
2016-03-09 20:10:03canjobearsetrecipients: + canjobear, serhiy.storchaka
2016-03-09 20:10:03canjobearsetmessageid: <1457554203.88.0.0908332368522.issue26522@psf.upfronthosting.co.za>
2016-03-09 20:10:03canjobearlinkissue26522 messages
2016-03-09 20:10:03canjobearcreate