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 barry
Recipients Arfrever, alexandre.vassalotti, barry, josh.r, kitterma, nadeem.vawda, pitrou, python-dev, serhiy.storchaka
Date 2016-01-11.18:36:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Jan 11, 2016, at 05:50 PM, Serhiy Storchaka wrote:

>Therefore my guess was true. There is a bug in Cython. It creates classes
>that can't be correctly unpickled or copied.

I don't think that's necessarily true.  Clearly the classes *can* be copied
and unpickled because they *are*, otherwise Cython builds would be failing for
a long time now, and I can find no evidence of that either in Debian/Ubuntu
packages which use Cython nor in upstream bug reports for Cython or the
affected packages.  It's just as likely that the assumptions of the
typeobject.c code are incorrect.

>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.

I am final testing a patch to typeobject.c that ifdefs that test out in 2.7,
3.5 and 3.6.  I think given the observed regressions, this is the right way to
go for now.  If you can figure out more detail about what's going on and can
adjust the change to avoid the regressions, then this code can be unifdef'd
away and fixed.
Date User Action Args
2016-01-11 18:36:55barrysetrecipients: + barry, pitrou, alexandre.vassalotti, nadeem.vawda, Arfrever, kitterma, python-dev, serhiy.storchaka, josh.r
2016-01-11 18:36:55barrylinkissue22995 messages
2016-01-11 18:36:54barrycreate