pip installs latest version in python2.7 environment #292
Comments
|
We were discussing this issue earlier today on openstack-qa in IRC: http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2020-03-26.log.html#t2020-03-26T19:40:06 Based on this discussion it appears that the issue with python 2.7 is caused by a temporary pypi issue. Apparently pbr supports python |
|
'python-requires' support in there for sure in pbr - https://github.com/openstack/pbr/blob/9257b6843568052be1dc1a5f3df6f629795e08b2/pbr/util.py#L116 'python-requires' is introduced from PEP440 version and until PEP345 it used to support 'requires-python also 'https://www.python.org/dev/peps/pep-0345/#requires-python I am not finding enough evidence that 'requires-python' is still supported or it is being removed. still checking.... |
|
The tricky thing is that pypi really doesn't return that metadata. |
|
3.0.1 has been pushed out with #293 applied |
|
Thank you! |
stestr 3.0.0 is released with drop the support of py2 but had some issue on setup.cfg metadata to restrict the installation on <py3 env. - mtreinish/stestr#292 This is fixed and released in 3.0.1 Let's cap the stestr version for py2 and py3 env also adding 3.0.0 in blacklist. Change-Id: Id0c2371c9ba37a3f19c2e0a3c121f99b54ac9ce8
* Update requirements from branch 'master'
- Merge "Fix on stestr requirements for non-py2"
- Fix on stestr requirements for non-py2
stestr 3.0.0 is released with drop the support of
py2 but had some issue on setup.cfg metadata to restrict
the installation on <py3 env.
- mtreinish/stestr#292
This is fixed and released in 3.0.1
Let's cap the stestr version for py2 and py3 env
also adding 3.0.0 in blacklist.
Change-Id: Id0c2371c9ba37a3f19c2e0a3c121f99b54ac9ce8
* Update pbr from branch 'master'
- Merge "Update python requires packaging metadata for package"
- Update python requires packaging metadata for package
The metadata field, 'python-requires' was introduced in PEP440 and
appears to have superseded 'requires-python'. [1] The metadata that pbr
uses for itself and it's test package was using the old incorrect field,
this commit updates it to be the proper metadata to show a working
example. To a certain extent it probably doesn't matter because it's very
unlikely someone will try to install pbr with python 2.5, but it's more
about making sure that pbr itself is leading by example and that it's own
config actually works.
[1] mtreinish/stestr#292
Change-Id: I5eb14d490a3731b6b95d7a1137c33ec2d73f193f
The metadata field, 'python-requires' was introduced in PEP440 and appears to have superseded 'requires-python'. [1] The metadata that pbr uses for itself and it's test package was using the old incorrect field, this commit updates it to be the proper metadata to show a working example. To a certain extent it probably doesn't matter because it's very unlikely someone will try to install pbr with python 2.5, but it's more about making sure that pbr itself is leading by example and that it's own config actually works. [1] mtreinish/stestr#292 Change-Id: I5eb14d490a3731b6b95d7a1137c33ec2d73f193f
Andrey-mp commentedMar 26, 2020
Issue description
pip2 installs stestr of version 3.0.0 in python2.7 env. It happens cause pypi doesn't have metadata tag 'data-requires-python'. This happens cause setup.cfg has key 'requires-python' instead of 'python-requires'
Expected behavior and actual behavior
expected: version <3.0.0 will be install by pip2.
actual: version 3.0.0 is installed by pip2
Steps to reproduce the problem
Run docker's image centos:7 and after installing pip try to install stestr by pip.
Specifications like the version of the project, operating system, or hardware
System information
stestr --version): 3.0.0python --version): 2.7pip freeze): doesn't matterAdditional information
The text was updated successfully, but these errors were encountered: