-
Notifications
You must be signed in to change notification settings - Fork 262
doc: Properly find the version #488
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
Conversation
The conf.py can't import nibabel if nibabel isn't installed, as is the case when installing nibabel for the first time.
In case you wonder why @jehane sent a pull-request for my commit, that's because I wrote the patch to help them and then completely forgot to open this pull-request. 😄 |
Current coverage is 93.97% (diff: 100%)@@ master #488 diff @@
==========================================
Files 166 166
Lines 21836 21836
Methods 0 0
Messages 0 0
Branches 2327 2327
==========================================
Hits 20520 20520
Misses 885 885
Partials 431 431
|
Looks reasonable. 👍 for merge. |
The change is reasonable, but I believe the docs will not build correctly without an installation of nibabel. What do you get if you try and build the docs when nibabel is not installed? |
Seems to work just fine with this patch applied. In a virtualenv, I did:
Then if I open |
I think in that case that
I get lots of errors like this in the doc build
and the API part of the documentation lists the submodules, but the content is empty. |
@bochecha - any comments here? For example, I wonder whether we just need a better error message if nibabel is not installed. |
I think this is the root of the problem. Indeed, I think when we had the problem originally with @jehane was because we had So maybe
Perhaps that error message could just tell people to run |
Inspired by nipy#488 with thanks.
Thanks for analyzing the problem a bit more. How about #503 ? |
The conf.py can't import nibabel if nibabel isn't installed, as is the
case when installing nibabel for the first time.