| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| IGNORED.pop(index) | ||
|
|
||
|
|
||
| def is_documented(name: str) -> bool: |
There was a problem hiding this comment.
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 a problem hiding this comment.
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 a problem hiding this comment.
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.
Sorry, something went wrong.
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
I plan on backporting this to prevent conflicts when things are removed from ignored_c_api.txt. Any objections? |
Sorry, something went wrong.
|
No objection to backporting. |
Sorry, something went wrong.
There was a problem hiding this comment.
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.
|
I assume that this is broken in strings too, for example: puts("PyAPI_FUNC(int) PySomething(void);"). There are plenty of ways to break the regular expressions. 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.
|
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.
|
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.
|
Thanks @ZeroIntensity for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
Sorry, something went wrong.
|
Sorry, @ZeroIntensity, I could not cleanly backport this to 3.14 due to a conflict. cherry_picker 1a7824a927f0706300af7bfc182884a43e2f587a 3.14 |
Sorry, something went wrong.
|
Sorry, @ZeroIntensity, I could not cleanly backport this to 3.13 due to a conflict. cherry_picker 1a7824a927f0706300af7bfc182884a43e2f587a 3.13 |
Sorry, something went wrong.
|
GH-142247 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 1a7824a)
… documentation (pythonGH-142102) (cherry picked from commit 1a7824a) Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
GH-142248 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 1a7824a)
… documentation (pythonGH-142102) (cherry picked from commit 1a7824a) Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
…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 <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 1a7824a) --------- Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
…ntation (pythonGH-142102) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
…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 <1324225+hugovk@users.noreply.github.com> (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 <zintensitydev@gmail.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> * Update Tools/check-c-api-docs/ignored_c_api.txt --------- Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
This adds a simple job requiring that any new public C APIs come with documentation, which should prevent things from slipping through the cracks each release.