➜

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 Arfrever, alexandre.vassalotti, barry, josh.r, kitterma, nadeem.vawda, pitrou, python-dev, serhiy.storchaka
Date 2016-01-11.17:50:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452534603.32.0.642259323532.issue22995@psf.upfronthosting.co.za>
In-reply-to
Content 
Therefore my guess was true. There is a bug in Cython. It creates classes that can't be correctly unpickled or copied.

The question is wherever we should replace TypeError with a warning in maintained releases, or remove this check at all? Here is a patch against 3.5 that replaces TypeError with a warning.
History
Date User Action Args
2016-01-11 17:50:03serhiy.storchakasetrecipients: + serhiy.storchaka, barry, pitrou, alexandre.vassalotti, nadeem.vawda, Arfrever, kitterma, python-dev, josh.r
2016-01-11 17:50:03serhiy.storchakasetmessageid: <1452534603.32.0.642259323532.issue22995@psf.upfronthosting.co.za>
2016-01-11 17:50:03serhiy.storchakalinkissue22995 messages
2016-01-11 17:50:02serhiy.storchakacreate