On 08/11/2011 12:28 PM, becky_lewis wrote:
> Just to add ...
>
> I ran through creating a virtualenv in the same manner as you:
>
>
> ipython is using the virtualenv when it can find them and the system
> wide packages when they are not in the virtualenv. Hope that helps you
> track down the pro
Just to add ...
I ran through creating a virtualenv in the same manner as you:
$ virtualenv SomeEnv
$ source SomeEnv/bin/activate
(SomeEnv)$ which pip
/home/user/virtual/SomeEnv/bin/pip
(SomeEnv)$ pip install ipython
Requirement already satisfied (use --upgrade to upgrade): ipython in /
usr/local
On 08/11/2011 11:39 AM, becky_lewis wrote:
> Hi,
>
> are you doing a pip install from within your virtualenv (sourcing the
> virtualenv and THEN installing ipython)?
>
Yes this is what I was doing.
My default ipython without virtualenv is now:
$ ipython -V
0.10
Within my virualenv it is now:
$
Hi,
are you doing a pip install from within your virtualenv (sourcing the
virtualenv and THEN installing ipython)?
Becky Lewis
On Aug 11, 9:59 am, Gelonida N wrote:
> Hi,
>
> Short version
> ==
> I have a system with ipython installed by my Ubuntu distribution
> I created a virtual
Hi,
Short version
==
I have a system with ipython installed by my Ubuntu distribution
I created a virtualenv with
> virtualenv ~/myenv
I installed ipython
> pip install ipython --upgrade
When using ipython I notice, that it does import the modules from my
default python setup and not
