>
> Of course, the question is whether all this matters. Is it important
> to save 8 bytes on each unicode object? Only testing would tell.
>
Last year, I tried to profile memory usage of web application in my company.
https://gist.github.com/methane/ce723adb9a4d32d32dc7525b738d3c31#investigati
Some of APIs are stated as "Deprecated since version 3.3, will be
removed in version 4.0:".
e.g. https://docs.python.org/3/c-api/unicode.html#c.PyUnicode_AS_UNICODE
So we will remove them (and wstr) at Python 4.0.
___
Python-Dev mailing list
Python-Dev@
My question for you: how on earth did you find this?! Speaking of a needle
in a haystack. Did you run some kind of analysis program that looks for
regexprs? (We've received some good reports from someone who did that
looking for possible DoS attacks.)
On Sun, Apr 1, 2018 at 6:49 PM, MRAB wrote:
On 4/1/2018 10:20 PM, Tim Peters wrote:
[MRAB [
A thread on python-ideas is talking about the prefixes of string literals,
and the regex used in IDLE.
Line 25 of Lib\idlelib\colorizer.py is:
stringprefix = r"(?i:\br|u|f|fr|rf|b|br|rb)?"
which looks slightly wrong to me.
This must be a
[MRAB [
> A thread on python-ideas is talking about the prefixes of string literals,
> and the regex used in IDLE.
>
> Line 25 of Lib\idlelib\colorizer.py is:
>
> stringprefix = r"(?i:\br|u|f|fr|rf|b|br|rb)?"
>
> which looks slightly wrong to me.
>
> The \b will apply only to the first choice.
A thread on python-ideas is talking about the prefixes of string
literals, and the regex used in IDLE.
Line 25 of Lib\idlelib\colorizer.py is:
stringprefix = r"(?i:\br|u|f|fr|rf|b|br|rb)?"
which looks slightly wrong to me.
The \b will apply only to the first choice.
Shouldn't it be more
