DOC: find kernelspec #13491
DOC: find kernelspec #13491
Conversation
Current coverage is 84.33%@@ master #13491 diff @@
==========================================
Files 138 138
Lines 51083 51083
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 43083 43083
Misses 8000 8000
Partials 0 0
|
|
Isn't there a way to say "use the same kernel as the one that is calling me"? |
|
I couldn't find anything like that immediately. Will look tonight. |
|
No matter, if I build the docs from that environment, the kernel will be named python2/3 anyhow, it's only when I select in the notebook the kernel itself (starting the notebook from another environment), that the name of this kernel will be different. |
|
There is a difference between kernel name and display name in the |
| @@ -116,6 +116,11 @@ def cleanup_nb(nb): | |||
| pass | |||
|
|
|||
|
|
|||
| def get_kernel(): | |||
| """Find kernals starting with ``name``.""" | |||
There was a problem hiding this comment.
This is a bit strange docstring
There was a problem hiding this comment.
Fixed. That was a leftover from a more complicated implementation I discarded.
TomAugspurger
force-pushed
the
doc-kernel
branch
from
cb967e1 to
8717d47
Compare
|
Let's give it another try! :-) |
|
https://travis-ci.org/pydata/pandas/jobs/138920776 is the build. |
|
Hmm, still not working: "Failed to convert source/html-styling.ipynb" in the logs |
|
Just saw that 😞, I'll look into it more later. |
xref #13487
Problem was the notebook was written with a python3 kernel, but the doc build is python2.
There are potentially problems here if you have non-default kernel names in your environment...