-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
using different source achieve different result when execute pipenv lock #1701
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
Comments
is |
Wait is this a bug? It looks like one package is hosted locally and it’s dependencies are on pypi. Both servers need to be in your pipfile. |
yes, of course. @kennethreitz
well, when I use |
is |
only the lock function be affected, the installing always give me result. @kennethreitz |
they are all in my enviroment. @techalchemy |
when the package is only a
|
this appears to be fixed in master (using bandersnatch as a mirror) |
I upgrade pipenv to the latest version 11.7.1. so I try to find something in the raw code:
I set the maybe this message can help you. |
Yes, that is a requirement :) |
ENV:
Pipenv version:
'11.6.0'
Pipenv location:
'/Library/Python/2.7/site-packages/pipenv'
PEP 508 Information:
the requirements.txt is this:
when pipfile is this:
excute pipenv lock --verbose, the result is wrong:
however, if I change the Pipfile like this(change the source):
or just add one extra source:
the result is right:
and the Pipfile.lock is:
while, the pipenv graph execute always correctly:
so, what is the problem or what should I do?
The text was updated successfully, but these errors were encountered: