##// END OF EJS Templates
Remove deprecated install_ext and ~/.ipython/extensions...
Remove deprecated install_ext and ~/.ipython/extensions As pointed out in #13722 loading extensions from this place have been deprecated for about 5 years, so time for removal. I understand this will likely make it too hard for some user who can't seem to be able to write 8 lines of configuration: $ cat mod.py pyproject.toml """ipython ext""" __version__ = "0.0.1" [build-system] requires = ["flit_core >=3.2,<4"] build-backend = "flit_core.buildapi" [project] name = "mod" dynamic = ["version", "description"] Those can be reminded that they can also modify their $PYTHONPATH, so that py files can be imported from their preferred folder. Closes #13722

File last commit:

r21874:3ffdf6f9
r27767:77a4bce7
Show More
ipython_console_highlighting.py
28 lines | 970 B | text/x-python | PythonLexer
/ IPython / sphinxext / ipython_console_highlighting.py
"""
reST directive for syntax-highlighting ipython interactive sessions.
"""
from sphinx import highlighting
from IPython.lib.lexers import IPyLexer
def setup(app):
"""Setup as a sphinx extension."""
# This is only a lexer, so adding it below to pygments appears sufficient.
# But if somebody knows what the right API usage should be to do that via
# sphinx, by all means fix it here. At least having this setup.py
# suppresses the sphinx warning we'd get without it.
metadata = {'parallel_read_safe': True, 'parallel_write_safe': True}
return metadata
# Register the extension as a valid pygments lexer.
# Alternatively, we could register the lexer with pygments instead. This would
# require using setuptools entrypoints: http://pygments.org/docs/plugins
ipy2 = IPyLexer(python3=False)
ipy3 = IPyLexer(python3=True)
highlighting.lexers['ipython'] = ipy2
highlighting.lexers['ipython2'] = ipy2
highlighting.lexers['ipython3'] = ipy3