docker / docker/docker-py

Dependencies problem when using pipenv lock for 3.3.0

Open
#2,021 4 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.2k
Forks
1.7k
Avg merge
13d 8h
Merged PRs (30d)
2

Description

I have used the following Pipfile to generate Pipfile.lock:

[[Source]]
url = 'https://pypi.python.org/simple'
verify_ssl = true
name = 'pypi'

[requires]
python_version = '3.6'

[packages]
pytest = '*'
docker = '*'
#docker = '==3.2.1'

If not specifying the version for docker (Actually download 3.3.0), I met the following dependencies problem when executing "pipenv lock", but the command will be successful if i specify the docker's version is '3.2.1'.
I am using the latest version of pipenv ("11.10.1"), and host machine i am using is Mac OS Sierra (10.12.6)

$ 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 pypiwin32==219,==220
Tried: 219, 219, 219, 219, 219, 219, 219, 219, 219, 219, 219, 219, 219, 220, 220, 223, 223
There are incompatible versions in the resolved dependencies.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report from the shown Pipfile using Python 3.6 and docker 3.3.0, then inspect the generated Pipfile.lock and the pipenv lock output. Trace why the resolver requests incompatible pypiwin32 versions 219 and 220, compare the result with docker 3.2.1, and consider the issue done when the unpinned dependency set locks successfully or the incompatibility is clearly reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.