C:\\Users\\danie01\\fox\\test\\robotframework>pipenv install --python 3.5
Creating a virtualenv for this project...
Pipfile: C:\\Users\\danie01\\fox\\test\\robotframe
Can you delete your old virtualenv C:\Users\danie01\.virtualenvs
Check the version of python inside Pipfile
[requires]
python_version = "3.5"
After go to your project to create again your virtualenv
cd C:\Users\danie01\fox\test\robotframework
pipenv install
This helped me when installing on Raspberry Pi 3B+ on Raspbian.
export PIPENV_TIMEOUT=9999
pipenv install requests
try doing pipenv --rm
- removes virtual environment
then pipenv shell
- this will again initiate virtual env
then pipenv install
again
worked for me
Depending on where you're running the pipenv install
command, set env variable PIP_NO_CACHE_DIR
to off
. In my case, I set this in my Dockerfile by having a line ENV PIP_NO_CACHE_DIR=false
before RUN pipenv install
I was using the url = "https://pypi.tuna.tsinghua.edu.cn/simple"
, and for each dependence installed, I would have a timeout error. When I changed the url to simple worked.
[[source]]
name = "pypi"
url = "https://pypi.python.org/simple"
verify_ssl = true
pipenv
ran a subprocess, and that process took longer than the default 15 minutes, then expect.py
was told to wait for a newline but it hit the timeout and here you are. First step is to increasing the TIMEOUT value in:
PIPENV_TIMEOUT
https://pipenv.readthedocs.io/en/latest/advanced/#configuration-with-environment-variables
PIPENV_INSTALL_TIMEOUT
Max number of seconds to wait for package installation.
Defaults to 900 (15 minutes), a very long arbitrary time.
If it's hanging forever, then the question becomes: What was pipenv told to do that results in a block? Use the --verbose
flag to tell pipenv to tell you what it's doing that results in a hang.
#try
export PIPENV_INSTALL_TIMEOUT=9000