Closed NyanKiyoshi closed 6 years ago
Please tell me if I can do anything to get you more debug information.
Edit: look like the issue is from the condition line 109 that is not handling the case where the location is None
.
https://github.com/pypa/pipenv/blob/ab107e2104e53870557b2d0cde16fe2505c88f30/pipenv/core.py#L106-L111
I think a temporary workaround is to not use the virtualenv created by yourself. But just cd
to your project directory and pipenv install
directly, and pipenv will create virtualenv automatically, which you can activate later by pipenv shell
.
Same happening here when running pipenv install
in travis install
phase. Didn't happen in previous pipenv version
@carlosdanielcsantos It may because travis is running under an activated virtualenv by default.
Somehow downgrading then upgrading again pipenv did the trick (older version weren't working too, but with other errors). Pipenv
was a fresh latest version install. Not sure what happened, that's really odd. Never had this issue before with pipenv.
make sure you install with --upgrade
on travis when you install everything, but there is also a logic error in that code
@techalchemy do you mean when installing pipenv
? Because I can't find any --upgrade
flag in pipenv install
@techalchemy I can reproduce this in 2018.10.9
by:
virtuanlenv testdir
source testdir/bin/activate
and cd testdir
pipenv install requests
I can't reproduce this by the latest master branch, the recent several PR may fix this.
Happening for me as well now, a little odd tho, because it worked normally for couple runs and then it started to throw this error. Using: pipenv-2018.10.9
.
I downgraded to pipenv-2018.5.18
and it seems to be working.
All versions between 2018.6.25
and 2018.10.9
don't work.
This was fixed by #2953 and #2972, sorry for the issue folks -- we will have a bugfix release out tomorrow
Thanks all for the detailed reports and for your patience!
Really strange; I encountered this today again... Like @admix, I found that uninstalling and installing again fixed it. I had previously created and updated environments with this installation as recently as 2 days ago. Running Catalina if it makes any difference (installed on release day, so that's not new either).
I too have just encountered this issue. Also running on MacOS Catalina. Uninstalling and reinstalling pipenv (via pip uninstall/install) doesn't seem to help. Activating previously created environments works, it's just creation of new virtualenvs with pipenv that doesn't work.
I also have this popping up today after upgrading to Catalina.
After upgrading to Catalina, $ pipenv install
was not working. Here was my system info:
$ pipenv --version
pipenv, version 2018.11.26
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.1
BuildVersion: 19B88
This was the fix for me:
$ brew upgrade pipenv
$ pipenv --version
pipenv, version 2018.11.26
Strange, because the pipenv version doesn't seem to have changed at all. However after upgrading with brew, $ pipenv install
worked as expected. Maybe it fixed some symlink or path issue for me?
That solution resolved the issue for me, thanks!
One of my teammates ran into this on Catalina. Uninstall and reinstalling pipenv
via brew did not work. These steps fixed it for us...
python_version = "3.7"
pipenv install
. (This happened to use python 3.7.5
otherwise we were going to try pipenv install --python 3.7.5
)pipenv install
still succeeds.thank you @abaldwin88 it works! Nothing else worked for me on Catalina.
@abaldwin88 that worked for me as well. Having this in my Pipfile:
[requires]
python_version = "3.7"
caused it to try using 3.7.3, but removing that section from the Pipfile and re-running pipenv install
caused it to try using 3.7.2, which worked. Is that a new bug?
I'm using pipenv, version 2018.11.26
.
Versions
pip==18.1 pipenv==2018.10.9
Issue description
When trying to do
install
operations withpipenv
, I get the following error:TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType
. Pipenv was just installed.Expected result
Install packages.
Actual result
Steps to replicate
Run
pipenv install
with or without giving packages.Pipenv version:
'2018.10.9'
Pipenv location:
'/home/sayuri/development/sailing/saleor-venv/lib/python3.6/site-packages/pipenv'
Python location:
'/home/sayuri/development/sailing/saleor-venv/bin/python'
Python installations found:
3.7.0
:/usr/bin/python3.7
3.7.0
:/usr/bin/python3.7m
3.6.6
:/home/sayuri/development/sailing/saleor-venv/bin/python3
3.6.6
:/home/sayuri/development/sailing/saleor-venv/bin/python
3.6.6
:/home/sayuri/development/sailing/saleor-venv/bin/python3.6
3.6.6
:/usr/bin/python3.6
3.6.6
:/usr/bin/python3.6m
2.7.15
:/usr/bin/python2.7
PEP 508 Information:
System environment variables:
ANDROID_HOME
LANG
DISPLAY
INVOCATION_ID
EDITOR
COLORTERM
ANDROID_SDK_ROOT
MOZ_PLUGIN_PATH
ANDROID_AVD_HOME
XDG_VTNR
VIRTUAL_ENV
XDG_SESSION_ID
USER
PWD
HOME
MUSIC_PATH
JOURNAL_STREAM
DESKTOP_STARTUP_ID
MAIL
WINDOWPATH
TERM
SHELL
ANDROID_SWT
COLORFGBG
XDG_SEAT
SHLVL
WINDOWID
LOGNAME
DBUS_SESSION_BUS_ADDRESS
XDG_RUNTIME_DIR
XAUTHORITY
PATH
PS1
LC_TIME
OLDPWD
_
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/home/sayuri/development/sailing/saleor-venv/bin:/home/sayuri/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/sayuri.local/bin:/opt/android-sdk//tools:/opt/android-sdk//platform-tools:/home/sayuri/.gem/ruby/2.5.0/bin
SHELL
:/bin/bash
EDITOR
:vim
LANG
:en_US.UTF-8
PWD
:/home/sayuri/development/sailing/saleor
VIRTUAL_ENV
:/home/sayuri/development/sailing/saleor-venv
Contents of
Pipfile
('/home/sayuri/development/sailing/saleor/Pipfile'):Contents of
Pipfile.lock
('/home/sayuri/development/sailing/saleor/Pipfile.lock'):