Message 75488 - Python tracker

➜

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	andrewmcnamara
Recipients	amigalemming, andrewmcnamara, belopolsky, effbot, loewis
Date	2008-11-04.01:24:38
SpamBayes Score	2.2096785e-05
Marked as misclassified	No
Message-id	<1225761881.01.0.261617904104.issue416670@psf.upfronthosting.co.za>
In-reply-to

Content
One reason why this issue has been having less impact is that a bug in some versions of the copy.py code meant it was ignoring the __deepcopy__ stubs and using the pickle logic to copy _sre objects - so, if you run the right python version, compiled regular expressions and match objects deepcopy without problems. On the 2.4 branch (release24-maint), changeset 38430 introduced the bug that prevents the class __deepcopy__ exception-raising stubs being found. As an aside, I don't understand why the _sre objects should be pickleable, but not deepcopy-able.

One reason why this issue has been having less impact is that a bug in 
some versions of the copy.py code meant it was ignoring the 
__deepcopy__ stubs and using the pickle logic to copy _sre objects - 
so, if you run the right python version, compiled regular expressions 
and match objects deepcopy without problems.

On the 2.4 branch (release24-maint), changeset 38430 introduced the bug 
that prevents the class __deepcopy__ exception-raising stubs being 
found.

As an aside, I don't understand why the _sre objects should be 
pickleable, but not deepcopy-able.

History
Date	User	Action	Args
2008-11-04 01:24:41	andrewmcnamara	set	recipients: + andrewmcnamara, loewis, effbot, belopolsky, amigalemming
2008-11-04 01:24:41	andrewmcnamara	set	messageid: <1225761881.01.0.261617904104.issue416670@psf.upfronthosting.co.za>
2008-11-04 01:24:39	andrewmcnamara	link	issue416670 messages
2008-11-04 01:24:38	andrewmcnamara	create