nbsphinx: WARNING: Pygments lexer name 'ipython3' is not known
I get thousands of warnings:
WARNING: Pygments lexer name 'ipython3' is not known
when I run make html
after adding 'nbsphinx'
to extensions
.
This happens even with an empty index.rst
file (it seems to find my .ipynb_checkpoints
folder).
python 3.5.1
ipython 4.1.1
nbconvert 4.1.0
jupyter 1.0.0
pygments 2.1
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 7
- Comments: 17 (9 by maintainers)
Commits related to this issue
- Fix syntax highlighting error. This follows https://github.com/spatialaudio/nbsphinx/issues/24 — committed to harpolea/r3d2 by IanHawke 8 years ago
- enabled syntax highlighting, following this bug: https://github.com/spatialaudio/nbsphinx/issues/24 — committed to GPflow/GPflow by jameshensman 8 years ago
- work around a bug in conda Discussion of issue: https://github.com/spatialaudio/nbsphinx/issues/24#issuecomment-187172022 Root cause: https://github.com/ContinuumIO/anaconda-issues/issues/1430 — committed to danking/hail by danking 7 years ago
- work around a bug in conda Discussion of issue: https://github.com/spatialaudio/nbsphinx/issues/24#issuecomment-187172022 Root cause: https://github.com/ContinuumIO/anaconda-issues/issues/1430 — committed to danking/hail by danking 7 years ago
- Fix all docs warnings (#1693) * eliminate warning in getting_started.rst * all warnings are errors * use anonymous links instead of named links * fix indentation of list item * fix a vari... — committed to hail-is/hail by danking 7 years ago
- in docs, improve three-way linking between type and representations (#1691) * eliminate warning in getting_started.rst * all warnings are errors * use anonymous links instead of named links ... — committed to hail-is/hail by danking 7 years ago
- Fix all docs warnings (#1693) * eliminate warning in getting_started.rst * all warnings are errors * use anonymous links instead of named links * fix indentation of list item * fix a vari... — committed to liameabbott/hail by danking 7 years ago
- in docs, improve three-way linking between type and representations (#1691) * eliminate warning in getting_started.rst * all warnings are errors * use anonymous links instead of named links ... — committed to liameabbott/hail by danking 7 years ago
- DOC: install ipython to build RST code blocks properly Examples built from Jupyter notebooks use ipython3 in RST code blocks. This means ipython must be installed for sphinx (particularly pygments) t... — committed to pycalphad/pycalphad by bocklund 7 years ago
- DOC: install ipython to build RST code blocks properly Examples built from Jupyter notebooks use ipython3 in RST code blocks. This means ipython must be installed for sphinx (particularly pygments) t... — committed to pycalphad/pycalphad by bocklund 7 years ago
- Remove IPython lexer workaround The issue described in https://github.com/spatialaudio/nbsphinx/issues/24 seems to be resolved by https://github.com/ContinuumIO/anaconda-issues/issues/1430 — committed to bryanwweber/thermostate by bryanwweber 6 years ago
- Enable notebook syntax highlighting The symptom is that local builds correctly have syntax highlighting in the output builds, but on RTD, they are lacking. Based on research from readthedocs/readthe... — committed to Lnaden/QCArchiveExamples by Lnaden 5 years ago
- several changes, see rest of commit message - grammatical small changes. Tried to get a more consistent use of words, punctuation etc. I tried not to touch sentences where I was unsure of whether ... — committed to razofz/nabo by razofz 5 years ago
- Updated Docs with ipython pygments lexar. See https://github.com/spatialaudio/nbsphinx/issues/24 — committed to phockett/ePSproc by phockett 4 years ago
- fix: Pygments lexer name 'ipython3' is not known — committed to MegEngine/Documentation by ChaiByte 3 years ago
- add ipython to dev requirements cf https://github.com/spatialaudio/nbsphinx/issues/24 — committed to eWaterCycle/ewatercycle by bvreede 3 years ago
- Add tutorial to documentation (#117) * add chapters to doc * add example notebook to the branch * add nbsphinx to dependencies * move notebook to docs instead of rst * small typoes * a... — committed to eWaterCycle/ewatercycle by bvreede 3 years ago
- COMP: Enable IPython.sphinxext.ipython_console_highlighting To address: ``` ConvertNumPyArrayToitkImage.ipynb:: WARNING: Pygments lexer name 'ipython3' is not known ``` per: - https://github.com/s... — committed to thewtex/ITKSphinxExamples by thewtex 2 years ago
- Fix syntax highlighting in doc examples https://github.com/spatialaudio/nbsphinx/issues/24 — committed to eltos/xplt by eltos 2 years ago
- Fix broken console highlighting extension https://github.com/spatialaudio/nbsphinx/issues/24 — committed to asreview/asreview by J535D165 2 years ago
I had to add
'IPython.sphinxext.ipython_console_highlighting'
toextensions
in myconf.py
. Somehow the old IPython docs have this info but the new ones don’t.Adding
'**.ipynb_checkpoints'
toexclude_patterns
fixed the other problem.Thanks!
A new issue appeared very recently, see #687.
@adamjstewart
ipywidgets
should only be required if there are widgets in the notebooks, more specifically, if there is someapplication/vnd.jupyter.widget-state+json
data.If you have widgets, you somehow have to provide the appropriate JavaScript files, which is done automatically if
ipywidgets
is available or manually withnbsphinx_widgets_path
, see https://nbsphinx.readthedocs.io/en/0.8.9/code-cells.html#Interactive-Widgets-(HTML-only).If none of your notebooks has any widgets but the warning is still shown, please let me know, because that may be a bug.
And yes, if you want to have code highlighting in code cells, you’ll have to install IPython, see https://nbsphinx.readthedocs.io/en/0.8.9/installation.html#Pygments-Lexer-for-Syntax-Highlighting.
expected behavior:
ipython
package'ipython3'
lexer is available without additional actions to be takenyour observed behavior:
ipython
'ipython3'
lexer is not availableTherefore, I suspect there is a bug somewhere. I don’t know how the “registration” process of the lexer is supposed to work, but it definitely shows different behavior on different systems.
For me, on Linux/Debian shows the expected behavior. It works also for the automatic build on readthedocs.