This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steven.daprano
Recipients bup, steven.daprano
Date 2022-01-11.22:21:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641939690.2.0.458597892912.issue46350@roundup.psfhosted.org>
In-reply-to
Content
It is better to raise each issue in its own ticket.

You seem to have three distinct issues here:

- The issue listed in the title, which I don't understand. A demonstration of the issue would be helpful.

- The unrelated(?) issue of bad \N{} escapes, which appears to have nothing to do with regexes, but maybe I'm wrong? In any case, whether this is regular expressions or plain old strings, it seems reasonable to me to limit \N{} to ASCII-only (Unicode guarantees that code point names are ASCII) and some reasonable length. I can't imagine the Unicode consortium ever deciding on a name > 255 characters, it wouldn't be practical.

- The difference in normalisation between group names and identifiers.
History
Date User Action Args
2022-01-11 22:21:30steven.dapranosetrecipients: + steven.daprano, bup
2022-01-11 22:21:30steven.dapranosetmessageid: <1641939690.2.0.458597892912.issue46350@roundup.psfhosted.org>
2022-01-11 22:21:30steven.dapranolinkissue46350 messages
2022-01-11 22:21:30steven.dapranocreate