# Cryptic 3.11 deprecation notice in the \`re\` module doc

**URL:** <https://discuss.python.org/t/cryptic-3-11-deprecation-notice-in-the-re-module-doc/20903>\
**Category:** Documentation\
**Created:** [November 9, 2022, 4:37pm UTC](https://discuss.python.org/t/cryptic-3-11-deprecation-notice-in-the-re-module-doc/20903 "2022-11-09T16:37:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kentzo](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/kentzo/32/4713_2.png) [@Kentzo](https://discuss.python.org/u/Kentzo)\
**Post date:** [November 9, 2022, 4:37pm UTC](https://discuss.python.org/t/cryptic-3-11-deprecation-notice-in-the-re-module-doc/20903/1 "2022-11-09T16:37:53Z")

</div>

I’m confused by the following [notice](https://docs.python.org/3/library/re.html#index-25):

> Deprecated since version 3.11: Group _id_ containing anything except ASCII digits.

After some digging I found the related [PR](https://github.com/python/cpython/issues/91760).

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](https://docs.python.org/3/library/re.html#re.sub):

> Deprecated since version 3.11: Group _id_ containing anything except ASCII digits. Group names containing non-ASCII characters in bytes replacement strings.

---

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [November 9, 2022, 6:50pm UTC](https://discuss.python.org/t/cryptic-3-11-deprecation-notice-in-the-re-module-doc/20903/2 "2022-11-09T18:50:13Z")

</div>

That’s a good observation. Would you mind helping out a bit and submit a PR for this?

---

<div class="post-metadata">

**Author:** ![Kentzo](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/kentzo/32/4713_2.png) [@Kentzo](https://discuss.python.org/u/Kentzo)\
**Post date:** [November 10, 2022, 12:27am UTC](https://discuss.python.org/t/cryptic-3-11-deprecation-notice-in-the-re-module-doc/20903/3 "2022-11-10T00:27:21Z")

</div>

> <https://github.com/python/cpython/pull/99311>
>
> \<!--
> Thanks for your contribution!
> Please read this comment in its entirety. I…t's quite important.
> 
> \# Pull Request title
> 
> It should be in the following format:
> 
> \`\`\`
> gh-NNNNN: Summary of the changes made
> \`\`\`
> 
> Where: gh-NNNNN refers to the GitHub issue number.
> 
> Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.
> 
> \# Backport Pull Request title
> 
> If this is a backport PR (PR made against branches other than \`main\`),
> please ensure that the PR title is in the following format:
> 
> \`\`\`
> \[X.Y\] \<title from the original PR\> (GH-NNNN)
> \`\`\`
> 
> Where: \[X.Y\] is the branch name, e.g. \[3.6\].
> 
> GH-NNNN refers to the PR number from \`main\`.
> 
> \--\>
> 
> 
> 
> \* Issue: gh-99308

> <https://github.com/python/cpython/pull/99310>
>
> \<!--
> Thanks for your contribution!
> Please read this comment in its entirety. I…t's quite important.
> 
> \# Pull Request title
> 
> It should be in the following format:
> 
> \`\`\`
> gh-NNNNN: Summary of the changes made
> \`\`\`
> 
> Where: gh-NNNNN refers to the GitHub issue number.
> 
> Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.
> 
> \# Backport Pull Request title
> 
> If this is a backport PR (PR made against branches other than \`main\`),
> please ensure that the PR title is in the following format:
> 
> \`\`\`
> \[X.Y\] \<title from the original PR\> (GH-NNNN)
> \`\`\`
> 
> Where: \[X.Y\] is the branch name, e.g. \[3.6\].
> 
> GH-NNNN refers to the PR number from \`main\`.
> 
> \--\>
> 
> 
> 
> \* Issue: gh-99308