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

Pip does not seem to be handling deep requirements correctly #4160

Closed
lingrlongr opened this issue Dec 5, 2016 · 4 comments
Closed

Pip does not seem to be handling deep requirements correctly #4160

lingrlongr opened this issue Dec 5, 2016 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation C: dependency resolution About choosing which dependencies to install

Comments

@lingrlongr
Copy link

  • Pip version: pip 9.0.1
  • Python version: 2.7.10
  • Operating System: mac (el capitan)

Description:

Pip does not seem to be handling deep requirements correctly.

What I've run:

# requirements.txt
awscli<1.11.0
botocore<1.5.0
pipdeptree

The pinnings are set to allow for bug fixes but prevent new features.

pip install -r requirements.txt
pipdeptree
Warning!!! Possibly conflicting dependencies found:
* awscli==1.10.67
 - botocore [required: ==1.4.57, installed: 1.4.81]
------------------------------------------------------------------------
awscli==1.10.67
  - botocore [required: ==1.4.57, installed: 1.4.81]
    - docutils [required: >=0.10, installed: 0.12]
    - jmespath [required: <1.0.0,>=0.7.1, installed: 0.9.0]
    - python-dateutil [required: <3.0.0,>=2.1, installed: 2.6.0]
      - six [required: >=1.5, installed: 1.10.0]
  - colorama [required: >=0.2.5,<=0.3.7, installed: 0.3.7]
  - docutils [required: >=0.10, installed: 0.12]
  - rsa [required: >=3.1.2,<=3.5.0, installed: 3.4.2]
    - pyasn1 [required: >=0.1.3, installed: 0.1.9]
  - s3transfer [required: <0.2.0,>=0.1.0, installed: 0.1.9]
    - botocore [required: <2.0.0,>=1.3.0, installed: 1.4.81]
      - docutils [required: >=0.10, installed: 0.12]
      - jmespath [required: <1.0.0,>=0.7.1, installed: 0.9.0]
      - python-dateutil [required: <3.0.0,>=2.1, installed: 2.6.0]
        - six [required: >=1.5, installed: 1.10.0]
    - futures [required: <4.0.0,>=2.2.0, installed: 3.0.5]
libxml2-python==2.9.3
nose==1.3.7
nose-machineout2==0.5.1
pipdeptree==0.8.0
  - pip [required: >=6.0.0, installed: 9.0.1]
setuptools==3.6
yum-metadata-parser==1.1.4

I expected that pip would honor the pinning to botocore==1.4.57 since that's more restrictive, and within range, of <1.5.0.

@lingrlongr
Copy link
Author

lingrlongr commented Dec 6, 2016

@pradyunsg
Copy link
Member

This is expected behavior.

This is a bug.


This issue is a duplicate of #775, which is tracked in #988. This issue may be closed as a duplicate of #988.

@dstufft
Copy link
Member

dstufft commented Mar 30, 2017

Closing as a duplicate of #988.

@dstufft dstufft closed this as completed Mar 30, 2017
@pradyunsg pradyunsg added the C: dependency resolution About choosing which dependencies to install label Jan 21, 2018
@lock
Copy link

lock bot commented Jun 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation C: dependency resolution About choosing which dependencies to install
Projects
None yet
Development

No branches or pull requests

3 participants