You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipenv cannot be locked currently due to a dependency conflict. The issue boils down to a dependency on an obsolete version boto3 coming from impresso-commons. The boto3 package needs to be pinned to a more recent version in the impresso-commons package.
Locking [dev-packages] dependencies…
Building requirements...
Resolving dependencies...
✔ Success!
Locking [packages] dependencies…
Building requirements...
Resolving dependencies...
✘ Locking Failed!
[ResolutionFailure]: File "/home/romanell/.pyenv/versions/3.6.7/lib/python3.6/site-packages/pipenv/resolver.py", line 785, in _main
[ResolutionFailure]: resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages)
[ResolutionFailure]: File "/home/romanell/.pyenv/versions/3.6.7/lib/python3.6/site-packages/pipenv/resolver.py", line 753, in resolve_packages
[ResolutionFailure]: requirements_dir=requirements_dir,
[ResolutionFailure]: File "/home/romanell/.pyenv/versions/3.6.7/lib/python3.6/site-packages/pipenv/resolver.py", line 736, in resolve
[ResolutionFailure]: req_dir=requirements_dir
[ResolutionFailure]: File "/home/romanell/.pyenv/versions/3.6.7/lib/python3.6/site-packages/pipenv/utils.py", line 1386, in resolve_deps
[ResolutionFailure]: req_dir=req_dir,
[ResolutionFailure]: File "/home/romanell/.pyenv/versions/3.6.7/lib/python3.6/site-packages/pipenv/utils.py", line 1093, in actually_resolve_deps
[ResolutionFailure]: resolver.resolve()
[ResolutionFailure]: File "/home/romanell/.pyenv/versions/3.6.7/lib/python3.6/site-packages/pipenv/utils.py", line 818, in resolve
[ResolutionFailure]: raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.
Alternatively, 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.
ERROR: Could not find a version that matches botocore<1.17.45,<1.20.0,<2.0a.0,>=1.12.36,>=1.17.44,>=1.19.5 (from boto3==1.16.5->-r /tmp/pipenvzctljgmirequirements/pipenv-k5yk6ed5-constraints.txt (line 11))
Tried: [...]
Skipped pre-versions: 1.0.0a1, 1.0.0a2, 1.0.0a3, 1.0.0b1, 1.0.0b2, 1.0.0b3, 1.0.0rc1, 1.0.0rc1
There are incompatible versions in the resolved dependencies:
botocore<1.17.45,>=1.17.44 (from aiobotocore==1.1.2->s3fs==0.5.1->-r /tmp/pipenvzctljgmirequirements/pipenv-k5yk6ed5-constraints.txt (line 14))
botocore<1.20.0,>=1.19.5 (from boto3==1.16.5->-r /tmp/pipenvzctljgmirequirements/pipenv-k5yk6ed5-constraints.txt (line 11))
botocore<2.0a.0,>=1.12.36 (from s3transfer==0.3.3->boto3==1.16.5->-r /tmp/pipenvzctljgmirequirements/pipenv-k5yk6ed5-constraints.txt (line 11))
The text was updated successfully, but these errors were encountered:
Pipenv cannot be locked currently due to a dependency conflict. The issue boils down to a dependency on an obsolete version boto3 coming from impresso-commons. The boto3 package needs to be pinned to a more recent version in the impresso-commons package.
The text was updated successfully, but these errors were encountered: