-
-
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 not resolving 2 editable pkgs with a dependency between them #4323
Comments
I believe this was resolved, can you check with |
I tried the reproducer given in the initial comment; it still fails, albeit with a different error. output
$ pipenv --supportPipenv version: Pipenv location: setuptools version: Python location: OS Name: User pip version: user Python installations found:
PEP 508 Information:
System environment variables:
Pipenv–specific environment variables: Debug–specific environment variables:
Contents of [[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true
[dev-packages]
[packages]
pkga = {editable = true,path = "."}
pkgb = {editable = true,path = "./../pkgb"}
[requires]
python_version = "3.7"
|
@chrisroat I wonder if recent work on constraint files is affecting it on this version, would you be able to check if it worked with |
Actually sorry, I just tried it and it still wasn't working in |
Yeah, fwiw it works if I take the install_requires `'pkgb==0.0.1' from the other setup.py. It appears that this constraint gets interpreted by the pip resolver + resolvelib to look for that package in the resolution phase and doesn't detect that it was also told to install the editable dependency with the same name. |
I worked out a PR that fixes the issue at hand, but I am not sure about any subtilties where the |
Issue description
Installing two local editable packages, where one depends on the other, fails to resolve the dependency. I tried both with and without a version requirement on the dependency. (Report below includes the version requirement.)
Expected result
Both packages get installed in my environment.
Actual result
Locking Failed!
It literally has these two lines in the output:
Full output
Steps to replicate
Three files in 2 subdirectories:
$ pipenv --support
Pipenv version:
'2020.6.2'
Pipenv location:
'/home/croat/.local/lib/python3.7/site-packages/pipenv'
Python location:
'/usr/bin/python3.7'
Python installations found:
3.7.5
:/usr/bin/python3.7m
3.7.5
:/usr/bin/python3.7
3.6.9
:/usr/bin/python3.6m
3.6.9
:/usr/bin/python3
3.6.9
:/usr/bin/python3.6
2.7.17
:/usr/bin/python2
2.7.17
:/usr/bin/python2.7
PEP 508 Information:
System environment variables:
CLUTTER_IM_MODULE
CONDA_SHLVL
NVM_DIR
CONDA_EXE
XDG_MENU_PREFIX
LANG
HISTIGNORE
HISTCONTROL
DISPLAY
HISTTIMEFORMAT
OLDPWD
GNOME_SHELL_SESSION_MODE
EDITOR
COLORTERM
NVM_CD_FLAGS
BASH_SILENCE_DEPRECATION_WARNING
USERNAME
XDG_VTNR
SSH_AUTH_SOCK
S_COLORS
_CE_M
XDG_SESSION_ID
USER
DESKTOP_SESSION
QT4_IM_MODULE
TEXTDOMAINDIR
GNOME_TERMINAL_SCREEN
PWD
HOME
CONDA_PYTHON_EXE
TEXTDOMAIN
SSH_AGENT_PID
QT_ACCESSIBILITY
XDG_SESSION_TYPE
XDG_DATA_DIRS
_CE_CONDA
XDG_SESSION_DESKTOP
GJS_DEBUG_OUTPUT
GTK_MODULES
VISUAL
WINDOWPATH
TERM
SHELL
VTE_VERSION
QT_IM_MODULE
XMODIFIERS
IM_CONFIG_PHASE
NVM_BIN
XDG_CURRENT_DESKTOP
GPG_AGENT_INFO
GNOME_TERMINAL_SERVICE
XDG_SEAT
SHLVL
GDMSESSION
GNOME_DESKTOP_SESSION_ID
LOGNAME
DBUS_SESSION_BUS_ADDRESS
XDG_RUNTIME_DIR
XAUTHORITY
XDG_CONFIG_DIRS
PATH
PS1
HISTSIZE
GJS_DEBUG_TOPICS
HISTFILESIZE
SESSION_MANAGER
GTK_IM_MODULE
_
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/home/croat/miniconda3/condabin:/home/croat/.nvm/versions/node/v14.3.0/bin:/home/croat/google-cloud-sdk/bin:/home/croat/bin:/home/croat/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SHELL
:/bin/bash
EDITOR
:emacs
LANG
:en_US.UTF-8
PWD
:/home/croat/multipackage_deps/pkga
Contents of
Pipfile
('/home/croat/multipackage_deps/pkga/Pipfile'):The text was updated successfully, but these errors were encountered: