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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-101100: Test docs in nit-picky mode #102513
gh-101100: Test docs in nit-picky mode #102513
Changes from all commits
ed0540b
4e2ef71
d1ce7f9
238dfc2
b97f25b
1465769
460d83f
bd7dbd6
15b6b1b
dded66d
e14191b
255a67f
742e29a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Especially since this list will (hopefully) get rather long (though using globs will help reduce it), IMO it would be cleaner to store the list of file/directory globs in a separate file (e.g. a text file in the
Doc/
directory), one path/glob per line, and then pipe in and iterate over the lines here (touch
-ing each one, of course).That would make it easier and more visible to update without going digging, and would also make it way easier for other tooling, scripts, etc. to use it as well, and if an option is added to upstream Sphinx, we could simply switch to reading it in the
conf.py
instead of having to convert it to a whole other format (which could also create problems with backports).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, possibly even a bash file that touches them. Anyway, will leave that for a follow-up so we can get this merged and see how it works in action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like the real problem is that this is documented as Python data, when it is in fact C data (a flag, specifically). So perhaps this should stay how it is, until the real problem is fixed (especially since doing so won't break external links, as the generated fragment should be the same.