Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/ipython/ipython/issues/1171/ below:

Recognise virtualenvs · Issue #1171 · ipython/ipython · GitHub

A recurring issue, which I've just added to the FAQ - a standard installation of IPython won't recognise when you're in a virtualenv. Various workarounds are showing up, but it would be good to work out of the box.

The root of the problem is that the installation sets the shebang line of ipython to #!/usr/bin/python. If it's #!/usr/bin/env python, virtualenvs work as expected. (I don't know what the status is on Windows)

A few possible ways to deal with this:

• Get an option added to distutils/packaging/setuptools/distribute to control the shebang line written. Long term at best.
• For Linux distributions, the shebang could be replaced as a step in the packaging.
• Contribute ipython-awareness to virtualenv, so if IPython is installed, it will copy the script and update the shebang line when you create a virtualenv.
• Detect when we're in a virtualenv, and add the relevant paths to sys.path. This is suboptimal, because it only affects importable libraries, not the interpreter itself (e.g. if I make a Python 2.6 virtualenv, IPython will still start with the default Python 2.7).

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4