New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cryptic deprecation notice in the re module #99308
Comments
GH-99310 is a backport of this pull request to the 3.11 branch. |
Maybe @CAM-Gerlach can review this? It does look like the original PR left some unclear deprecation notices. |
I'd reviewed the linked #99311 previously, but while I didn't explicitly state it in my initial review, yeah the textual clarifications I suggest there should also be made in the other two places from the same original PR where a change in the allowed values for Also, since this was an unusual case where a deprecation made in one released turned into a change in the next, the changes will likely need to be manually backported with the |
Kentzo commentedNov 10, 2022
•
edited by bedevere-bot
Documentation
I'm confused by the following notice:
After some digging I found the related PR.
With the notice as is I would assume that non-ASCII digits would be interpreted as a name, but after reading the PR it's obvious that it cannot be the case since names must contain ASCII letters and digits.
Perhaps it's better to rewrite it to match the notice for re.sub:
See https://discuss.python.org/t/cryptic-3-11-deprecation-notice-in-the-re-module-doc/20903
The text was updated successfully, but these errors were encountered: