GH-101100: Resolve reference warnings in library/stdtypes.rst#138420
Conversation
|
I think that the right fix for this is to add anchors instead of removing references. |
Sorry, something went wrong.
|
@serhiy-storchaka I've generally been hesitant to suppress cross-references, but I think all the instances here make sense, given their context. Are there some specific ones you would revert? A |
Sorry, something went wrong.
All of them? See my suggestion #101100 (comment) . After implementing it the references in footnotes will gone, as they will become the part of the method description, and many other references will became working. After that we can check what remains. |
Sorry, something went wrong.
# Conflicts: # Doc/library/stdtypes.rst
|
(Resolved conflict) |
Sorry, something went wrong.
cde19e5
into
python:main
Nov 22, 2025
|
Thanks @AA-Turner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
Sorry, something went wrong.
…ythonGH-138420) (cherry picked from commit cde19e5) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
Sorry, @AA-Turner, I could not cleanly backport this to |
Sorry, something went wrong.
…s.rst (pythonGH-138420) (cherry picked from commit cde19e5) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Sorry, something went wrong.
📚 Documentation preview 📚: https://cpython-previews--138420.org.readthedocs.build/