Fix Sphinx warnings in re library docs#107044
Conversation
|
LGTM. But I wait for another review from better English writer before merge. |
|
Thanks @wulmer for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Thanks @wulmer for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
|
Sorry, @wulmer and @AlexWaygood, I could not cleanly backport this to |
|
Sorry @wulmer and @AlexWaygood, I had trouble checking out the |
|
Thanks @wulmer for the PR, and @AlexWaygood for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
|
GH-107046 is a backport of this pull request to the 3.12 branch. |
(cherry picked from commit 149748e) Co-authored-by: wulmer <wulmer@users.noreply.github.com>
|
Ah, I see the conflict for the 3.11 backport is (at least partly) due to the fact that the |
|
@wulmer, are you able to take care of the 3.11 backport? |
@AlexWaygood : I think so. I have read the comments above about the |
Either is absolutely fine :) |
|
GH-107055 is a backport of this pull request to the 3.11 branch. |
(cherry picked from commit 149748e)
As addition to PR #106995 this PR fixes the remaining Sphinx warnings.
There are two issues:
re.UdefinitionscanfFor 2., I chose to use exclamation mark to disable the reference link, but I am not sure if
scanfshould be included into #106948.📚 Documentation preview 📚: https://cpython-previews--107044.org.readthedocs.build/