GH-101100: Fix reference warnings for socket methods#110114
Conversation
serhiy-storchaka
left a comment
There was a problem hiding this comment.
I think that in all cases where it refers to socket() as a function, it should keep :func: role.
Sorry, something went wrong.
serhiy-storchaka
left a comment
There was a problem hiding this comment.
I think that the problem is that if you use a reference starting with ., Sphinx switches in more strict mode that checks the role type, so :func:`.socket` does not find the class declaration. But :func:`socket.socket` may work.
Sorry, something went wrong.
|
@AA-Turner Please could you resolve the conflicts? Then I think we're ready to merge. |
Sorry, something went wrong.
serhiy-storchaka
left a comment
There was a problem hiding this comment.
I restored the use of the .. class:: directive for socket. It fixes rendering for "the socket constructor". The :func: references work when specify the full qualified name.
Also fixed references for few more methods.
Sorry, something went wrong.
|
Thanks @AA-Turner for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
Sorry, something went wrong.
…nGH-110114) (cherry picked from commit ffe1b2d) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
…nGH-110114) (cherry picked from commit ffe1b2d) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
…n#110114) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
…n#110114) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
This doesn't tackle the constants.
📚 Documentation preview 📚: https://cpython-previews--110114.org.readthedocs.build/en/110114/library/socket.html