Oh I think I figured out what happened. I didn't install the new -whl which
is whats used in the virtualenv.
On Fri Nov 21 2014 at 5:44:00 PM Stefano Rivera wrote:
> Hi Jack (2014.11.18_11:53:09_+0200)
> > 1.5.6-3 doesn't seem to be working over here even on a fresh virtualenv
>
> Works for me:
Hi Jack (2014.11.18_11:53:09_+0200)
> 1.5.6-3 doesn't seem to be working over here even on a fresh virtualenv
Works for me:
$ cat test.sh
#!/bin/sh
virtualenv ve
. ve/bin/activate
pip install pillow
pip uninstall pillow
$ ./test.sh
Running virtualenv with interpreter /usr/bin/python2
New python
1.5.6-3 doesn't seem to be working over here even on a fresh virtualenv
Installing collected packages: pillow
Found existing installation: Pillow 2.4.0
Can't uninstall 'Pillow'. No files were found to uninstall.
- Jack Laxson
Control: reassign -1 python-pip-whl
Control: found -1 python-pip-whl/1.5.6-2
> (I am unsure if this is because of interaction of pip with the virtualenv,
> so I am reporting against python-virtualenv, not python-pip. Feel free
> to reassign!)
Yeah, this is actually a pip bug.
So, it looks like t
Package: python-virtualenv
Version: 1.11.6-2
Severity: important
Dear Maintainer,
(I am unsure if this is because of interaction of pip with the virtualenv,
so I am reporting against python-virtualenv, not python-pip. Feel free
to reassign!)
When creating a virtualenv, the version of pip that ge
5 matches
Mail list logo