Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

remove %install_ext

See original GitHub issue

%install_ext is now deprecated. For 5.0 we can completely remove all reference of it.

(marking as sprint friendly)

Issue Analytics

State:
Created 8 years ago
Comments:15 (12 by maintainers)

Top GitHub Comments

1reaction

Carreaucommented, Aug 25, 2016

Just one aspect of install_ext isn’t covered: that extensions added via install_ext were available in all kernels, extensions added via pip/conda have to be added (and updated) in all individual kernels (I use envs as kernels and have a lot of them 😦)

You can use pip install --prefixwith the right things on your $PATH that will work covers this use case.

0reactions

takluyvercommented, Aug 26, 2016

With conda environments, pip install --user will work, because conda envs still see packages in your user site-packages (unless you’ve manually turned this off, as I have). If we keep adding ~/.ipython/extensions to sys.path for loading extensions, you could also pip install -t ~/.ipython/extensions.

I agree that it’s a bit inconvenient, but not enough to warrant making our own package manager.