| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Documentation build overview3 files changed ± c-api/import.html ± c-api/slots.html ± extending/newtypes.html |
Sorry, something went wrong.
| }; | ||
| is: | ||
|
|
||
| .. literalinclude:: ../../Include/cpython/import.h |
There was a problem hiding this comment.
Could you add a comment to import.h before the struct, warning that this is included in public docs?
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #159808.
@encukou suggested to just delete the PyTypeObject definition from the docs but I wasn't quite brave enough to do that. I could also see valid reasons for wanting to know what's in that type and just generally would prefer not to break old docs links.
Instead I added a comment to the end of the file in Doc/includes to more forcefully hint that private fields shouldn't be documented. The comment shouldn't show up in the built docs.