Skip to content
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 won't lock a file but there is no version clash #2720

Closed
LegoStormtroopr opened this issue Aug 8, 2018 · 2 comments
Closed

Pipenv won't lock a file but there is no version clash #2720

LegoStormtroopr opened this issue Aug 8, 2018 · 2 comments
Labels
Status: Needs More Information This issue does not provide enough information to take further action.

Comments

@LegoStormtroopr
Copy link

Pipenv won't lock a file but there is no version clash

Issue description

I can't make a Pipfile.lock, despite there being no inconsistencies. If I try a pipenv install --skip-lock everything is file, but locking is impossible.

I import dependencies that import dependencies that import asgiredis, and As far as I can see no library requires >2.1.3, but Pipenv is reporting that something does.

Expected result

A Pipfile.lock is generated

Actual result
sam:~/environment/git/myrepo (master) $ pipenv lock
Locking [dev-packages] dependencies...
Locking [packages] dependencies...

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Could not find a version that matches asgiref==1.1.2,~=1.1,~=1.1.2,~=2.3
Tried: 0.8, 0.9, 0.9.1, 0.10.0, 0.11.0, 0.11.0, 0.11.0, 0.11.1, 0.11.1, 0.11.2, 0.11.2, 0.12.0, 0.12.0, 0.12.1, 0.12.1, 0.13.0, 0.13.0, 0.13.2, 0.13.2, 0.13.3, 0.14.0, 0.14.0, 1.0.0, 1.0.0, 1.0.1, 1.0.1, 1.1.0, 1.1.0, 1.1.1, 1.1.1, 1.1.2, 1.1.2, 2.0.0, 2.0.0, 2.0.1, 2.0.1, 2.1.0, 2.1.0, 2.1.1, 2.1.1, 2.1.2, 2.1.2, 2.1.3, 2.1.3, 2.1.4, 2.1.4, 2.1.5, 2.1.5, 2.1.6, 2.1.6, 2.2.0, 2.2.0, 2.3.0, 2.3.0, 2.3.1, 2.3.1, 2.3.2, 2.3.2
There are incompatible versions in the resolved dependencies.

sam:~/environment/git/myrepo (master) $ pipenv graph | grep asgi
  - asgi-redis [required: Any, installed: 1.4.3]
    - asgiref [required: ~=1.1.2, installed: 1.1.2]
    - asgiref [required: ~=1.1, installed: 1.1.2]
      - asgiref [required: ~=1.1, installed: 1.1.2]
      - asgiref [required: ~=1.1, installed: 1.1.2]
        - asgiref [required: ~=1.1, installed: 1.1.2]
Steps to replicate

Honestly, I'm not sure

@uranusjr
Copy link
Member

uranusjr commented Aug 9, 2018

Please at leasst provide a Pipfile that can produce a similar result. With so little information, we can say little than “this never happened to us”.

@uranusjr uranusjr added the Status: Needs More Information This issue does not provide enough information to take further action. label Aug 9, 2018
@techalchemy
Copy link
Member

Closing due to not enough information to determine any further actions, likely will be fixed in this release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs More Information This issue does not provide enough information to take further action.
Projects
None yet
Development

No branches or pull requests

3 participants