when install some package, it shows Collecting package_name
, it does not go on, just stoped there, without any error message.
when with option --no-cache-dir
, or with sudo
it works well.
I work on os x 10.11.1, with homebrewed python3.
Any ideas?
Run it with -vvv
to get a better idea of where it's stopping.
Thanks for the reply.
It showed as below:
$ pip3 install -vvv request
Collecting request
Getting page https://pypi.python.org/simple/request/
Starting new HTTPS connection (1): pypi.python.org
"GET /simple/request/ HTTP/1.1" 200 272
After typing pip3 -vvv list
, following the list, it shows:
Starting new HTTPS connection (1): pypi.python.org
"GET /pypi/pip/json HTTP/1.1" 200 46090
then got stuck there.
Running pip3 --no-cache-dir
has no problem.
same issue, but I'm using pip installed with pyenv
Looks like a duplicate of #3148.
It would be interesting to see where it is hanging and why, maybe add a break point to https://github.com/pypa/pip/blob/7.1.2/pip/_vendor/cachecontrol/controller.py#L88 and sees where it hangs ?
@xavfernandez
after debug, i found code stuck at
https://github.com/pypa/pip/blob/develop/pip/_vendor/requests/sessions.py#L605
print r
shows
<Response [200]>
i have no idea what this mean
p.s.
when with --no-cache-dir, the if not stream:
was not entered.
I found this problem probably had something to do with cache directory or .lock file in cache directory.
When I try pip3 list
, after listing all installed package, pip just hung there, didn't exit.
Then I remove http directory in /User/myname/Library/Caches/pip/, pip3 exited immediately.
try pip3 list
again, it worked fine.
the third pip3 list
just went back to initial situation.
It looks the same as this issue, my pip version = 7.1.2
https://github.com/pypa/pip/issues/2787
@Russell-Jones @xavfernandez @brosner @alex
below is my debug result.
there was exception:
https://github.com/quxiaowei/demo/blob/master/debug#L77
and got stuck at the last line:
https://github.com/quxiaowei/demo/blob/master/debug#L98.
which was trying to open the .lock file.
hoping it will help!
close by mistake!
this problem does not happen on version 8.0.2
It might have been solved by #3382
Same here
I don't think this was solved by #3382. It is still around in pip 9.0.1
, see #3532, of which this is probably a duplicate.
Most helpful comment
I don't think this was solved by #3382. It is still around in
pip 9.0.1
, see #3532, of which this is probably a duplicate.