-
Notifications
You must be signed in to change notification settings - Fork 232
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
Requirement py>=1.4.22 is too low #105
Comments
Note : pip does not have a dependency resolver : pypa/pip#988 ; it needs our help.. |
Up for doing a PR? |
Sure, but do you want the incomplete solution of bumping up to |
This is now much worse, as the The result is it is especially difficult to depend on |
`pytest-xdist` depends on `pytest>=3`. `pytest 3.0.0` requires `py>=1.4.29` and latest pytest requires `py>=1.4.33`. Thus it is unnecessary for pytest-xdist to include a requirement on `py>=1.4.22` Fixes pytest-dev#105
`pytest-xdist` depends on `pytest>=3`. `pytest 3.0.0` requires `py>=1.4.29` and latest pytest requires `py>=1.4.33`. Thus it is unnecessary for pytest-xdist to include a requirement on `py>=1.4.22` Fixes pytest-dev#105
setup.py
requirespy>=1.4.22
, andpytest>=2.7.0
, however pytest 2.7.0 setup.py requirespy>=1.4.25
.This causes problems as pip resolutions is not very good.
If someone installs
pytest-xdist
&pytest
2.7.0 together in that order, pip will usepy>=1.4.22
and ignorepy>=1.4.25
. You can see that at https://travis-ci.org/jayvdb/my-ci-test/jobs/187902155All is well if pytest-xdist bumps the requirement up to
py>=1.4.25
, and someone wants to install pytest 2.7.0 : See https://travis-ci.org/jayvdb/my-ci-test/builds/187901866 , which fakes that situation by first intallingpy==1.4.25
However it fails again if someone wants to use the latest
pytest
, as it requires py>=1.4.29`. See https://travis-ci.org/jayvdb/my-ci-test/jobs/187913569#L241The text was updated successfully, but these errors were encountered: