-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add tooling to report method inheritance cascades for objects #93
Conversation
Still have to manually update based on doctest results, but at least it's easy to keep it fresh/accurate -- just copy/paste from the failed doctest output.
Constrain pytest doctests to just README, which Sphinx can't easily reach. Only installing docs requirements for 3.7 b/c Sphinx>=2 doesn't support 3.4.
No reason to repeat the nearly identical job content
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.
this would make a great sphinx plugin
Have to use the Python console style for now, for cross-platform compat (currently the shell execution is hardcoded to bash). Also, it looks like there's no way to add 'setup' code to run, so for now the preamble with runpy &c. seems to be unavoidable.
Oy, just what I need, another side project! 😛 |
*Much* cleaner!
Codecov Report
@@ Coverage Diff @@
## master #93 +/- ##
=======================================
Coverage ? 100%
=======================================
Files ? 3
Lines ? 101
Branches ? 0
=======================================
Hits ? 101
Misses ? 0
Partials ? 0 Continue to review full report at Codecov.
|
Ok, that's nice and concise, now. Syntax should be pretty straightforward; just add any objects of interest to Any idea how to sniff out where the Any desired changes to the output? |
Uses doctests to indicate whether the inheritance information in the docs needs updating.
Output of current POC.Now merged. See latest.Adds doctests to CI, both Travis and Azure.