Skip to content

Conversation

@AA-Turner
Copy link
Member

@AA-Turner AA-Turner commented Aug 3, 2023

The final PR in this series -- once all the "Resolve unreferenced footnotes" PRs are merged, we can enable Sphinx's nit-picky mode.

A

This also closes #3213.


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

@AA-Turner AA-Turner marked this pull request as draft August 3, 2023 02:04
@AA-Turner AA-Turner force-pushed the enable-nit-picky-mode branch from 208fa03 to 38944c0 Compare August 5, 2023 01:37
@AA-Turner AA-Turner marked this pull request as ready for review August 5, 2023 11:56
@AA-Turner AA-Turner merged commit ce3a330 into python:main Aug 5, 2023
@AA-Turner AA-Turner deleted the enable-nit-picky-mode branch August 5, 2023 11:59
@AA-Turner
Copy link
Member Author

Thanks for your help reviewing the references PRs (& fixing far more references yourself) @hugovk!

A

@hugovk
Copy link
Member

hugovk commented Aug 5, 2023

And thank you very much for finishing them all off!

Good we won't need #3213 :)

What do you think about annotating new warnings in PRs? That's number 3 from #3213.

@AA-Turner
Copy link
Member Author

I was instead going to just set -W by default (#3272) -- we could potentially only set -W in CI, and annotate warnings etc in PRs, but I wonder about author experience if PEPs that 'work' locally suddenly fail when making a PR.

A

@hugovk
Copy link
Member

hugovk commented Aug 5, 2023

Yes, I think setting -W ("turn warnings into errors") by default makes sense, doing the same both locally and for CI.

And for the CI, also SPHINXOPTS="-w sphinx-warnings.txt" to write them out to a file so they can be annotated in the PR? Will make it more visible where the error is coming from, without having to dig through logs and look up line numbers.

@CAM-Gerlach
Copy link
Member

Shouldn't -n be added too, to avoid introducing new broken ref warnings, since we're clean on those?

Also, FYI, this line setting the docutils warning level should be removed, as it is redundant with -W and interferes with e.g. --keep-going.

@AA-Turner
Copy link
Member Author

See #3272 (comment)

@CAM-Gerlach
Copy link
Member

Nice, thanks—forgot you could do that.

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