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

Version specifier on sub-requirement ignored if same requirement listed by parent without version specifier #4887

Closed
matt-hammond-001 opened this issue Nov 24, 2017 · 5 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@matt-hammond-001
Copy link

  • Pip version: 9.0.1
  • Python version: 2.7.14 (via Mac Ports)
  • Operating system: Mac OS 10.12.6

Description:

Installing a package X that specifies two requirements: Y and Z. Y has no version specifier. Requirement Z also specifies a requirement for Y, but includes a version specifier.

When installing X, the version specifier for Y that was given by package Z is ignored. It should not be. I would have expected pip to install a version of Y that matches the version specifier given by Z.

The specific situation where this has arisen is when currently cherrypy and cheroot are not installed, and six==1.10.0 is installed. Installing cherrypy==11.0.0 results in cheroot==5.10.0 being installed but six remains at 1.10.0 when it should have been upgraded to 1.11.0

This caused problems in this situation: https://travis-ci.org/bbc/pydvbcss/jobs/306781295

What I've run:

To setup up the situation:

$ pip uninstall cherrypy cheroot six
$ pip install six==1.10.0

Then install cherrypy and check dependencies sorted:

$ pip install cherrypy==11.0.0
$ pip check
cheroot 5.10.0 has requirement six>=1.11.0, but you have six 1.10.0.
@benoit-pierre
Copy link
Member

Probably a dupplicate of #988.

@pradyunsg
Copy link
Member

Indeed.

@matt-hammond-001
Copy link
Author

Thanks - so if I understand correctly, this behaviour is a feature, not a bug.

That is a shame, as it really feels counter-intuitive. However I'll close the ticket.

@pradyunsg
Copy link
Member

so if I understand correctly, this behaviour is a feature, not a bug.

@matt-hammond-bbc It is a (big) bug, not a feature.

@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 Jul 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jul 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
Projects
None yet
Development

No branches or pull requests

3 participants