[issue416670] MatchObjects not deepcopy()able

Change by admin : -- github: None -> 34351 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue416670] MatchObjects not deepcopy()able

Mark Lawrence breamore...@yahoo.co.uk added the comment: No reply to msg113202. -- nosy: +BreamoreBoy resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue416670

[issue416670] MatchObjects not deepcopy()able

Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +mrabarnett ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue416670 ___ ___

[issue416670] MatchObjects not deepcopy()able

Terry J. Reedy tjre...@udel.edu added the comment: The OP has no interest in this, there is no patch, and re2 is coming. Should we close this? -- nosy: +terry.reedy stage: - unit test needed versions: +Python 3.2 -Python 2.6, Python 2.7 ___ Python

[issue416670] MatchObjects not deepcopy()able

Martin v. Löwis [EMAIL PROTECTED] added the comment: As far as I can tell, there is no proposed patch. So this is out of scope for 2.5.3. -- versions: -Python 2.5.3 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue416670

[issue416670] MatchObjects not deepcopy()able

Changes by Andrew McNamara [EMAIL PROTECTED]: -- versions: +Python 2.5.3, Python 2.6 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue416670 ___ ___

[issue416670] MatchObjects not deepcopy()able

Andrew McNamara [EMAIL PROTECTED] added the comment: 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,

[issue416670] MatchObjects not deepcopy()able

Alexander Belopolsky [EMAIL PROTECTED] added the comment: A related issue419070 was closed with no resolution (or resolution did not survive the trip from SF), but it looks like the patch was rejected. Some work towards this issue was done in r21437, but 7 years later it is still marked as

[issue416670] MatchObjects not deepcopy()able

Amiga Lemming [EMAIL PROTECTED] added the comment: On Mon, 17 Mar 2008, Alexander Belopolsky wrote: Alexander Belopolsky [EMAIL PROTECTED] added the comment: A related issue419070 was closed with no resolution (or resolution did not survive the trip from SF), but it looks like the patch was

[issue416670] MatchObjects not deepcopy()able

Changes by Christian Heimes: -- versions: +Python 2.6 Tracker [EMAIL PROTECTED] http://bugs.python.org/issue416670 ___ Python-bugs-list mailing list Unsubscribe:

[issue416670] MatchObjects not deepcopy()able

Changes by Brett Cannon: -- nosy: -brett.cannon Tracker [EMAIL PROTECTED] http://bugs.python.org/issue416670 ___ Python-bugs-list mailing list Unsubscribe:

[issue416670] MatchObjects not deepcopy()able

Changes by Brett Cannon: -- dependencies: +Fix #416670: register SRE types Tracker [EMAIL PROTECTED] http://bugs.python.org/issue416670 ___ Python-bugs-list mailing

[issue416670] MatchObjects not deepcopy()able

Changes by Brett Cannon: -- dependencies: -Fix #416670: register SRE types Tracker [EMAIL PROTECTED] http://bugs.python.org/issue416670 ___ Python-bugs-list mailing