[issue10076] Regex objects became uncopyable in 2.5

2017-04-16 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue10076] Regex objects became uncopyable in 2.5

2017-04-16 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: New changeset fdbd01151dbd5feea3e4c0316d102db3d2a2a412 by Serhiy Storchaka in branch 'master': bpo-10076: Compiled regular expression and match objects now are copyable. (#1000) https://github.com/python/cpython/commit/fdbd01151dbd5feea3e4c0316d102db3d2a2a41

[issue10076] Regex objects became uncopyable in 2.5

2017-04-05 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- pull_requests: +1173 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue10076] Regex objects became uncopyable in 2.5

2017-04-05 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Since the pattern and the match objects can be considered as immutable, it is worth to implement __copy__ and __deepcopy__ returning the object itself. Proposed PR does this. It also fixes signatures of __deepcopy__ methods. Since copying didn't work in all

[issue10076] Regex objects became uncopyable in 2.5

2014-10-23 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- components: +Regular Expressions versions: +Python 3.4, Python 3.5 -Python 3.1 ___ Python tracker ___ ___

[issue10076] Regex objects became uncopyable in 2.5

2012-08-27 Thread Michael Shields
Michael Shields added the comment: It's not strictly necessary that re objects be copyable, but there's no reason to break it either. It's not strictly necessary that str or int be copyable either. This came up in code that had objects with a number of members, one of which was a regexp patt

[issue10076] Regex objects became uncopyable in 2.5

2012-08-26 Thread Matthew Barnett
Matthew Barnett added the comment: Is it necessary to actually copy it? Isn't the pattern object immutable? -- nosy: +mrabarnett ___ Python tracker ___ __

[issue10076] Regex objects became uncopyable in 2.5

2012-08-24 Thread Анхбаяр Лхагвадорж
Анхбаяр Лхагвадорж added the comment: Ding. -- nosy: +Анхбаяр.Лхагвадорж ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue10076] Regex objects became uncopyable in 2.5

2010-10-21 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue10076] Regex objects became uncopyable in 2.5

2010-10-14 Thread Senthil Kumaran
Senthil Kumaran added the comment: The patch looks reasonable to me. I was trying to find out why they got disabled after 2.5, but I don't see any reason. (There was an issue open and it was closed for no reason). So, I think, this should move forward, unless there is any technical objection

[issue10076] Regex objects became uncopyable in 2.5

2010-10-12 Thread Michael Shields
Michael Shields added the comment: Here's the patch. I updated the test case and release notes also. I'm a Google employee, so this patch is covered by whatever usual copyright arrangement we have with the PSF. -- keywords: +patch Added file: http://bugs.python.org/file19205/copy-pat

[issue10076] Regex objects became uncopyable in 2.5

2010-10-12 Thread Michael Shields
New submission from Michael Shields : For many years now, the sre module has provided __copy__ and __deepcopy__ modules that raise an exception ("cannot copy this pattern object") by default, with an #ifdef to enable their implementations. Until Python 2.5, these were simply unused. Since th