You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
sre_compile._optimize_unicode() needs a cleanup #57309
exceptIndexError:
# non-BMP characters; XXX now they should workreturncharset
sys.maxunicode != 65535 is now always true in Python 3.3
ifsys.maxunicode!=65535:
# XXX: negation does not work with big charsets# XXX2: now they should work, but removing this will make the# charmap 17 times biggerreturncharset
See the related commit: f39b26ca7f3d (from issue bpo-13054).
There are a lot of dead or suboptimal code in the re module. For example _sre.CODESIZE now can't be 2. We could cleanup the code as side effect of optimization.
Activity
vstinner commentedon Oct 4, 2011
The following comment is wrong,
sys.maxunicode != 65535 is now always true in Python 3.3
See the related commit: f39b26ca7f3d (from issue bpo-13054).
vstinner commentedon Jan 3, 2013
I don't know what to do with this issue. The code looks to work anyway, so I guess that it's safer to not touch it :-)
serhiy-storchaka commentedon Oct 21, 2013
There are a lot of dead or suboptimal code in the re module. For example _sre.CODESIZE now can't be 2. We could cleanup the code as side effect of optimization.