-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipenv clean
fails when pip freeze
produces output with comments
#2229
Comments
nelfin
added a commit
to nelfin/pipenv
that referenced
this issue
May 21, 2018
requirements.txt files (and by extension pipfreeze) can contain comment lines, but the stdout of pip freeze is used in a number of places with the assumption that every line contains a dependency declaration. This change adds an integration test that could trigger one of these cases that was the cause of the behaviour seen in issue pypa#2229.
nelfin
added a commit
to nelfin/pipenv
that referenced
this issue
May 21, 2018
Ref pypa#2229. This change only fixes the issue seen when calling `pipenv clean`. A future refactor should consolidate these behaviours (or use the actual parsing of lines from pip, i.e. FrozenRequirement, if we can rely on this API).
By the way, this also affects
|
Of course it does. It also fails with sync, if you haven’t noticed :) This is a failure when Pipenv prepares arguments to pass to pip, so any commands that installs and uninstalls things will be affected. ( |
uranusjr
pushed a commit
that referenced
this issue
May 25, 2018
requirements.txt files (and by extension pipfreeze) can contain comment lines, but the stdout of pip freeze is used in a number of places with the assumption that every line contains a dependency declaration. This change adds an integration test that could trigger one of these cases that was the cause of the behaviour seen in issue #2229.
uranusjr
pushed a commit
that referenced
this issue
May 25, 2018
Ref #2229. This change only fixes the issue seen when calling `pipenv clean`. A future refactor should consolidate these behaviours (or use the actual parsing of lines from pip, i.e. FrozenRequirement, if we can rely on this API).
uranusjr
pushed a commit
that referenced
this issue
May 31, 2018
requirements.txt files (and by extension pipfreeze) can contain comment lines, but the stdout of pip freeze is used in a number of places with the assumption that every line contains a dependency declaration. This change adds an integration test that could trigger one of these cases that was the cause of the behaviour seen in issue #2229.
uranusjr
pushed a commit
that referenced
this issue
May 31, 2018
Ref #2229. This change only fixes the issue seen when calling `pipenv clean`. A future refactor should consolidate these behaviours (or use the actual parsing of lines from pip, i.e. FrozenRequirement, if we can rely on this API).
This one is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pipenv update
: pipenv update fails if freeze output contains comments #1268do_clean
assumes that the output ofpip freeze
produces only requirement lines, but it can in some cases produce#
-prefixed comments (see https://github.com/pypa/pip/blob/729990c9869148f3f0098a2b2a0c0b92aefb8a69/src/pip/_internal/operations/freeze.py#L188 for one such example). It looks as though this was noticed and fixed forpipenv update
in 9.1.0 (see f322d93)$ python -m pipenv.help output
Pipenv version:
'2018.05.18'
Pipenv location:
'$HOME/.virtualenvs/pipenv-issue/local/lib/python2.7/site-packages/pipenv'
Python location:
'$HOME/.virtualenvs/pipenv-issue/bin/python'
Other Python installations in
PATH
:2.7
:$HOME/.virtualenvs/pipenv-issue/bin/python2.7
2.7
:$HOME/.virtualenvs/pipenv-issue/bin/python2.7
2.7
:/usr/bin/python2.7
3.5
:/usr/bin/python3.5m
3.5
:/usr/bin/python3.5
2.7.12
:$HOME/.virtualenvs/pipenv-issue/bin/python
2.7.12
:/usr/bin/python
2.7.12
:$HOME/.virtualenvs/pipenv-issue/bin/python2
2.7.12
:/usr/bin/python2
3.5.2
:/usr/bin/python3
PEP 508 Information:
System environment variables:
MANDATORY_PATH
XDG_GREETER_DATA_DIR
GNOME_DESKTOP_SESSION_ID
UPSTART_EVENTS
PYTHONDONTWRITEBYTECODE
LESSOPEN
XDG_SESSION_TYPE
QT_IM_MODULE
LOGNAME
USER
PATH
XDG_VTNR
GNOME_KEYRING_CONTROL
PS1
DISPLAY
LANG
TERM
SHELL
XDG_SESSION_PATH
XAUTHORITY
LANGUAGE
COMPIZ_CONFIG_PROFILE
SHLVL
QT_LINUX_ACCESSIBILITY_ALWAYS_ON
QT_QPA_PLATFORMTHEME
QT_ACCESSIBILITY
UPSTART_INSTANCE
CLUTTER_IM_MODULE
WINDOWID
SESSIONTYPE
XMODIFIERS
GPG_AGENT_INFO
HOME
QT4_IM_MODULE
GTK2_MODULES
XDG_SESSION_DESKTOP
SSH_AUTH_SOCK
XDG_RUNTIME_DIR
INSTANCE
COMP_WORDBREAKS
VTE_VERSION
GDMSESSION
IM_CONFIG_PHASE
UPSTART_JOB
UPSTART_SESSION
GNOME_KEYRING_PID
XDG_SEAT_PATH
LESSCLOSE
PIP_PYTHON_PATH
XDG_CURRENT_DESKTOP
XDG_SESSION_ID
DBUS_SESSION_BUS_ADDRESS
_
DEFAULTS_PATH
GTK_IM_MODULE
DESKTOP_SESSION
VIRTUAL_ENV
XDG_CONFIG_DIRS
GTK_MODULES
GDM_LANG
XDG_DATA_DIRS
PWD
JOB
LS_COLORS
XDG_SEAT
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:$HOME/.virtualenvs/pipenv-issue/bin:$HOME/.local/bin:$HOME/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:$HOME/.rvm/bin:$HOME/.rvm/bin
SHELL
:/usr/bin/fish
LANG
:en_AU.UTF-8
PWD
:$HOME
VIRTUAL_ENV
:$HOME/.virtualenvs/pipenv-issue
Expected result
Actual result
Steps to replicate
The text was updated successfully, but these errors were encountered: