4 ms·

I use virtualenv for all projects, and frequently destroy and recreate virtualenvs. iPython takes a good while to install; doing it over and over again in fresh

I use virtualenv for all projects, and frequently destroy and recreate virtualenvs. iPython takes a good while to install; doing it over and over again in fresh virtualenvs gets to be a chore, so I tend to do it only when I really need it. I dunno, is there a better way, maybe installing iPython globally, but rewriting the shebang line to use /usr/bin/env python?

tshepang 13y ago
You can always install it directly, and not in a virtualenv. Am I missing something?
- xnxn 13y ago
  That would require you to enable global site- packages for that virtualenv.
- Buttons840 13y ago
  If it's installed globally then it wont have access to the libraries installed only in the virtualenv. I think there's a way to work around this, but I haven't taken the time to look into it.
  - tshepang 13y ago
    Now I know what I missed.
  - eclipticplane 13y ago
    This should be fixed in the latest iPython versions. iPython is now virtualenv-aware -- it'll add your venv path at startup even if iPython is installed in global site-packages.
e12e 13y ago
AFAIK if you're using virtualenvs, you'd best bet would be various approaches to caching/proxying pypi. Won't help if the actual install (compile) times of ipython is a problem though.
takluyver 13y ago
A global installation of IPython now recognises if you start it with a virtualenv active, and adds the virtualenv to sys.path so that you can import modules installed there. It isn't limited to packages in the virtualenv - that is, it always behaves like you created the virtualenv with system-site-packages enabled, because it is importing its own modules from there. But for most interactive use, that's not a problem.