-
Notifications
You must be signed in to change notification settings - Fork 632
run doctests #2605
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
run doctests #2605
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2605 +/- ##
==========================================
+ Coverage 71.99% 73.01% +1.01%
==========================================
Files 107 109 +2
Lines 11914 12038 +124
==========================================
+ Hits 8577 8789 +212
+ Misses 3337 3249 -88
|
It’s unblocked again apparently! |
@ivirshup any way to force Azure to clear its cache or use a different runner? The “invalid instruction” error here probably comes from using a binary wheel compiled for a newer CPU. /edit: wow, 9 attempts. Maybe just dropping Python 3.8 will get us there. |
Scientific Python even deprecated Python 3.9 this month. Kill 3.8 please... |
For sure, but it won’t help with this issue, I had to merge #2687 for that. |
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.
Is this ready for review? I think it mostly looks good.
drop 3.8
If our dependencies have dropped support we can too.
Have you thought about doctestplus in the context of this PR?
You mean like anndata? 😆
yeah! |
@ivirshup ping |
TODO: check out doctest-plus, if it helps enough, switch to it, then merge |
f2c2a52
to
ad29ca5
Compare
OK, doctest-plus can’t even handle relative imports, and doesn’t respect It needs quite some work before it works for us. |
This PR adds the
--doctest-modules
flag to pytest and makes changes necessary to allow the doctests to run.Those changes include: