[issue39146] too much memory consumption in re.compile unicode

Zachary Ware added the comment: As mentioned on the attached PR, Python 2.7 has reached EOL and this can no longer be accepted. Thanks for the report and patch anyway! -- nosy: +zach.ware resolution: -> out of date stage: patch review -> resolved status: open -> closed

[issue39146] too much memory consumption in re.compile unicode

Change by Andy Lester : -- components: +Regular Expressions -Library (Lib) nosy: +ezio.melotti, mrabarnett ___ Python tracker ___ __

[issue39146] too much memory consumption in re.compile unicode

Zhipeng Xie <775350...@qq.com> added the comment: > but range() was here before ebd48b4f650d. before ebd48b4f650d, _optimize_unicode use xrange. So python2.7.8 is ok and python2.7.9 consume much memory in my test case. > Obviously there are other causes of the difference between 2.7 and 3.x.

[issue39146] too much memory consumption in re.compile unicode

Serhiy Storchaka added the comment: We usually do not backport optimizations to 2.7. It could be backported if a regression was introduced in one of 2.7 bugfixes, but range() was here before ebd48b4f650d. Also, range(0x1,0x10+1) takes only 32*2**16 = 2 MiB of memory. It is small in

[issue39146] too much memory consumption in re.compile unicode

Zhipeng Xie <775350...@qq.com> added the comment: Hi, I tracked it down and found that this problem was introduced in python2.7.9 by following commit: https://hg.python.org/cpython/rev/ebd48b4f650d -- nosy: +serhiy.storchaka ___ Python tracker

[issue39146] too much memory consumption in re.compile unicode

Change by Roundup Robot : -- keywords: +patch pull_requests: +17172 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17728 ___ Python tracker ___ __

[issue39146] too much memory consumption in re.compile unicode

Change by Zhipeng Xie <775350...@qq.com>: -- title: to much memory consumption in re.compile unicode -> too much memory consumption in re.compile unicode ___ Python tracker __