On 1/23/20 8:57 AM, John Fulton wrote: > What are projects doing about new linters working only with newer deps > or even python3 only? For example [1] [2]. Might it be OK to ignore > pep8 results on maintenance branches? > > Thanks, > John > > [1] > https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_82b/703943/1/check/openstack-tox-pep8/82b01fb/tox/pep8-1.log > > Ignoring ruamel.yaml: markers 'python_version == "3.4"' don't match > your environment > ERROR: ansible-lint 4.2.0 has requirement ruamel.yaml<1,>=0.15.34; > python_version < "3.7", but you'll have ruamel-yaml 0.13.14 which is > incompatible. > This actually isn't a pep8 issue, it's a pip install issue. It appears this job is installing a version of raumel that is not compatible with the Python version used. So it is rightly giving an error. It appears ansible-lint has a requirement for a version higher than the upper-constraint for stable/queens: https://opendev.org/openstack/requirements/src/branch/stable/queens/upper-constraints.txt#L204 We don't cap linters in the overall upper-constraints.txt file. It looks like the project may need to cap it at a version that is compatible with this stable branch version of things. Sean