gh-101100: Fix broken xrefs in fcntl module doc#115691
Merged
willingc merged 7 commits intopython:mainfrom Feb 25, 2024
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A few changes:
fcntl,ioctlandflocksystem calls are suppressed. Sphinx only complained about some, but even if it catalogued these somehow, it would likely have been incorrect.:const:LOCK_*refs. They appear nowhere else in the Python docs. Users should read the relevant Unix manpages.EACCESanEAGAINconstant references to data references in theerrnomodule.I'm inclined to move the rather large set of
:versionchanged:directives down near the bottom of the file, though for now I left them alone. Almost all of them just identify additions to the set of command constants, and are both platform- and Linux kernel-dependent. As such, they are probably going to be used infrequently. They aren't key to understanding how to use the module.📚 Documentation preview 📚: https://cpython-previews--115691.org.readthedocs.build/