tripleo-common-stable/train openstack-tox-py27 job failing with ERROR: Package 'Pygments' requires a different Python: 2.7.17 not in '>=3.5'

[Jesse Pretorius]

Sphinx requires Pygments>=2.0:
https://github.com/sphinx-doc/sphinx/blob/v1.8.5/setup.py#L21

Pygments removed py2 compatibility in https://github.com/pygments/pygments/commit/35544e2fc6eed0ce4a27ec7285aac71ff0ddc473

We need to pin Pygments<2.6.0

[Jesse Pretorius (jesse-pretorius)]

https://review.opendev.org/715168

[Sorin Sbarnea (ssbarnea)]

I guess is time for me to paste the email I send earlier:

I wanted to share a tox fix that any of you may have to do on if you encounter py27 jobs failing while py36 one passing.

Look at:

https://review.rdoproject.org/r/#/c/26102/3/tox.ini

Explanation:

About a month ago, upstream removed testing of constraints with py27 but they did not remove the already existing conditions specific to py27.

This was a trick to "persuading" people to drop py27 without causing a big outage on all of them. Soon they will also remove all conditions related to py27, so 99% of py27 will fail.

Mainly constraints from master are incompatible with py27.

As there are some places where we do need/want to keep the compatibility with both versions, we need to change constraints to use stable/train branch ones, the last version that supported py27.

Take a look at the change, it will make it much easier to put a fix whenever you encounter such a problem.

PS. You will find problems even if you are not using constraints and in most cases the solution is use python version conditionals in requirements.txt file to enforce pip to install the last version known to work with py27.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements rocky-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements stein-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements yoga-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements train-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements ussuri-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements victoria-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements xena-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/requirements zed-eom release.