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 scoder
Recipients Arfrever, alexandre.vassalotti, barry, josh.r, kitterma, nadeem.vawda, pitrou, python-dev, scoder, serhiy.storchaka
Date 2016-01-12.13:04:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for calling me in. I can confirm that the stack trace in points at a bug in Cython's own implementation (not the code it generates). It's deep-copying objects that don't support it (which doesn't normally have an impact because they aren't actually used). I'll try to fix that.

Given this specific case, i.e. deep-copying objects to death "by accident", however shows that this change is clearly a) helpful and b) harmful. It's going to help people write safer code, but it will also break existing working code that can't normally fail as it is and that people might not really want to (or even cannot) touch any more. Not really something for a backport, IMHO.
Date User Action Args
2016-01-12 13:04:56scodersetrecipients: + scoder, barry, pitrou, alexandre.vassalotti, nadeem.vawda, Arfrever, kitterma, python-dev, serhiy.storchaka, josh.r
2016-01-12 13:04:56scodersetmessageid: <>
2016-01-12 13:04:56scoderlinkissue22995 messages
2016-01-12 13:04:56scodercreate