GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||
GeezerVison is showing github.com — gh-141004: Add a CI job ensuring that new C APIs include documentation by ZeroIntensity · Pull Request #142102 · python/cpython Conversation
|
| IGNORED.pop(index) | ||
|
|
||
|
|
||
| def is_documented(name: str) -> bool: |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I think is_documented is a little different from is present. Why not improve the check to include verifying it's a doc declaration, i.e. if it's in the text check it's on the same line as the c:func:: etc.?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I thought about that, but I decided that it was a case of "practicality beats purity". Running Sphinx or using a regular expression will make this significantly slower, and probably won't save us much in practice.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
As a compromise, we could go ever simpler, just checking if :: and .. are in the same line as the API name.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Hugo van Kemenade <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
|
I plan on backporting this to prevent conflicts when things are removed from |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
No objection to backporting. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This currently picks up decelerations in comments, e.g. Py_OldFunction which is an example. This currently passes as the same example is used in the docs.
Edit: I wrote: ZeroIntensity#6
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I assume that this is broken in strings too, for example: We can't really get this to work perfectly without using an actual C parser. If those comments aren't causing problems for us, why bother? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
To clarify: I agree with eventually adding better handling, I just don't think it should be done here. I'd like this script to be as close as possible to the script used to generate the list in #141004. We can expand on this in a later iteration. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'm going to merge this. For changes regarding the mock C parsing here, please open a new issue and/or PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Thanks @ZeroIntensity for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @ZeroIntensity, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @ZeroIntensity, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-142247 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <[email protected]> (cherry picked from commit 1a7824a)
… documentation (pythonGH-142102) (cherry picked from commit 1a7824a) Co-authored-by: Peter Bierma <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]>
|
GH-142248 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <[email protected]> (cherry picked from commit 1a7824a)
… documentation (pythonGH-142102) (cherry picked from commit 1a7824a) Co-authored-by: Peter Bierma <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]>
…entation (GH-142102) (GH-142247) * gh-141004: Add a CI job ensuring that new C APIs include documentation (GH-142102) Co-authored-by: Hugo van Kemenade <[email protected]> (cherry picked from commit 1a7824a) --------- Co-authored-by: Hugo van Kemenade <[email protected]>
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <[email protected]>
…entation (GH-142102) (GH-142248) * gh-141004: Add a CI job ensuring that new C APIs include documentation (GH-142102) Co-authored-by: Hugo van Kemenade <[email protected]> (cherry picked from commit 1a7824a) * [3.13] gh-141004: Add a CI job ensuring that new C APIs include documentation (GH-142102) (cherry picked from commit 1a7824a) Co-authored-by: Peter Bierma <[email protected]> Co-authored-by: Hugo van Kemenade <[email protected]> * Update Tools/check-c-api-docs/ignored_c_api.txt --------- Co-authored-by: Hugo van Kemenade <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.