Skip to content

PEP 747: Fix Sphinx warnings#4908

Open
Secrus wants to merge 1 commit intopython:mainfrom
Secrus:pep-747-warnings
Open

PEP 747: Fix Sphinx warnings#4908
Secrus wants to merge 1 commit intopython:mainfrom
Secrus:pep-747-warnings

Conversation

@Secrus
Copy link
Copy Markdown
Contributor

@Secrus Secrus commented Apr 14, 2026

Ref: #4087

There were 3 references Sphinx 8.1+ was warning about:


📚 Documentation preview 📚: https://pep-previews--4908.org.readthedocs.build/

- #type_t reference was introduced in PR#3929, but was not used in the document text. Converted to a bullet point.
- #TypeIs reference was converted from #TypeIsPep, however it is now linked in code via a `typing` reference. Removed it.
- #forward_ref_normalization reference usage was removed in PR#3929, but the reference was left behind. Since it makes little sense without the usage, removed it.
Comment thread peps/pep-0747.rst

.. [#TypeIs]
:ref:`TypeIs[T] <typing:typeis>` is similar to bool
* :ref:`Type[T] <typing:type-brackets>` spells a class object
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bare bullet point in the footnotes section doesn't make much sense, why not remove it?

Also cc @davidfstr

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly - don't know. If you think that it makes little to no reason to leave it, I can remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants