'pipenv clean' fails when running in an existing virtualenv #3231
Labels
Comments
Hey @rectalogic, We did a quick check and this issue looks very darn similar to
This could be a coincidence, but if any of these issues solves your problem then I did a good job If not, the maintainers will get to this issue shortly. Cheers, |
Merged
@frostming just to be clear, we won't clean system packages with your fix, right? I'm not actually sure it is desired to clean packages from a non-pipenv controlled virtualenv /cc @uranusjr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
I create and activate my own virtualenv, pipenv reports it is running in an existing virtualenv. I install a package and then run
pipenv clean
which fails (it attempts to decode an empty string as JSON).Expected result
pipenv should clean the existing virtualenv
Actual result
Raises exception.
I set a breakpoint where it loads the json, and it looks like it created it's own virtualenv instead of using the active one:
However
/home/cureatr/.local/share/virtualenvs
directory is empty.Steps to replicate
$ pipenv --support
Pipenv version:
'2018.11.14'
Pipenv location:
'/home/cureatr/.local/lib/python2.7/site-packages/pipenv'
Python location:
'/usr/bin/python'
Python installations found:
3.6.6
:/usr/bin/python3.6
3.6.6
:/usr/bin/python3.6m
2.7.15rc1
:/usr/bin/python2.7
PEP 508 Information:
System environment variables:
PYTHONDONTWRITEBYTECODE
LESSOPEN
SSH_CLIENT
LOGNAME
USER
PATH
HOME
PS1
LANG
TERM
SHELL
SHLVL
PWD
CUREATR_SERVER
PYTHONFINDER_IGNORE_UNSUPPORTED
PROCESSOR_CONFIG
XDG_RUNTIME_DIR
PYTHONPATH
S_COLORS
TMUX
PIP_PYTHON_PATH
XDG_SESSION_ID
_
LS_COLORS
LESSCLOSE
CUREATR_EXTMSG
SSH_TTY
OLDPWD
CUREATR_HOME
CUREATR_WEB
PIP_SHIMS_BASE_MODULE
PIP_DISABLE_PIP_VERSION_CHECK
MAIL
SSH_CONNECTION
TMUX_PANE
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
SHELL
:/bin/bash
LANG
:en_US.UTF-8
PWD
:/tmp/testing
The text was updated successfully, but these errors were encountered: