-
-
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 fails to resolve dependencies for moto
#2847
Comments
This is a problem with |
Is it really a problem with Is it a bug or a feature? (I love pipenv, this is a serious question). |
Why don’t you jump in and contribute something if this is so simple to you :) |
@uranusjr I just wanted to say it technically is not a problem with I understand resolving dependencies is not a simple problem in general. Also from the output of Correct me if I'm getting something wrong, please. |
Well, unfortunately we are living in a real world, and have real-world problems :p Dependency resolution is not only non-trivial to implement, but also difficult for the computer to actually perform, algorithmically. Resolvers, therefore, generally need to make assumptions to make the process fast enough (and, you know, Pipenv’s is already not very fast to begin with). The assumption Pipenv makes here is tha each requirement subtree (in this case moto and its dependencies) should have its root (moto) correctly specified a non-conflicting requirement set, and if no version specification is provided, the latest should work. pip also makes this assumption (this error message comes from pip), and would be (IMO) considered quite common in the Python packaging community. Following this line of thought, it would be entirely moto’s responsibility to its requirements and make sure they don’t conflict with each other. The error message Pipenv emits could be more informational (it is also difficult to do, unfortunately), but ultimately, in the current ecosystem Python packaging is in, the problem needs to be resolved by moto. (And I should mention they already did! Shout out to its wonderful maintainers.) |
If the consensus is this is a problem with |
Issue description
I have a very simple
Pipfile
for a new project, it includes nothing exceptmoto
as a dev dependency, butpipenv lock
fails to resolve dependencies. Themoto
library installs fine with vanillapip
.I deleted
~/.cache/pipenv
and tried withpipenv lock --clear
as suggested in the FAQ, but it didn't make any difference.Expected result
I expected dependencies to be resolved and a
Pipfile.lock
to be generated.Actual result
$ pipenv lock --verbose
Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
Pipfile
$ pipenv --support
Pipenv version:
'2018.7.1.dev0'
Pipenv location:
'/home/bjmc/.local/lib/python3.6/site-packages/pipenv'
Python location:
'/usr/bin/python3'
Python installations found:
3.6.5
:/usr/bin/python3.6m
3.6.5
:/usr/bin/python3.6
2.7.15rc1
:/usr/bin/python2.7
PEP 508 Information:
System environment variables:
CLUTTER_IM_MODULE
LS_COLORS
LESSCLOSE
XDG_MENU_PREFIX
LANG
DISPLAY
AWS_PROFILE
GNOME_SHELL_SESSION_MODE
COLORTERM
DESKTOP_AUTOSTART_ID
USERNAME
XDG_VTNR
SSH_AUTH_SOCK
XDG_SESSION_ID
USER
DESKTOP_SESSION
QT4_IM_MODULE
TEXTDOMAINDIR
GNOME_TERMINAL_SCREEN
PWD
HOME
TEXTDOMAIN
SSH_AGENT_PID
QT_ACCESSIBILITY
XDG_SESSION_TYPE
XDG_DATA_DIRS
XDG_SESSION_DESKTOP
GTK_MODULES
WINDOWPATH
TERM
SHELL
VTE_VERSION
QT_IM_MODULE
XMODIFIERS
IM_CONFIG_PHASE
XDG_CURRENT_DESKTOP
GPG_AGENT_INFO
GNOME_TERMINAL_SERVICE
XDG_SEAT
SHLVL
LANGUAGE
GDMSESSION
GNOME_DESKTOP_SESSION_ID
LOGNAME
DBUS_SESSION_BUS_ADDRESS
XDG_RUNTIME_DIR
XAUTHORITY
XDG_CONFIG_DIRS
PATH
SESSION_MANAGER
LESSOPEN
GTK_IM_MODULE
OLDPWD
_
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/home/bjmc/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SHELL
:/bin/bash
LANG
:en_GB.UTF-8
PWD
:/home/bjmc/Sandbox/lambda-auth
Contents of
Pipfile
('/home/bjmc/Sandbox/lambda-auth/Pipfile'):The text was updated successfully, but these errors were encountered: