Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork291
WIP: point Sphinx directly at real modules#415
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
See comments inpyparsing#411.
This requires "annotations" from __future__, which doesn't exist inPython 3.6. Might be nice to have someday though.
I'm inclined to keep the |
That makes sense. What would you think about still referencing the individual modules directly for Sphinx? It would make it more straightforward to include documentation for module-level variables like The alternative, if we wanted to document any variables, would be to put their documentation directly in common_html_entity:ParserElement=common_html_entity"""Convenience parser for common HTML entities""" common_html_entity:ParserElement# type: ignore[no-redef]"""Convenience parser for common HTML entities""" |
Looking at this, but late now - will pick up some time tomorrow. |
Please don't remove the replaced_by_pep8 decorators. As I said, I'm going to use those to emit DeprecationWarnings starting in pyparsing 3.1.0 |
See comments in#411.