Tox basepython and Python3

Sean McGinnis sean.mcginnis at gmx.com
Tue May 12 14:51:23 UTC 2020


On 5/12/20 9:44 AM, Sorin Sbarnea wrote:
> I recently discovered that this problem goes even deeper, please read all comments on https://github.com/tox-dev/tox/issues/1565
>
> Due to this it seems to be impossible to define zuul jobs that use a specific python version regardless the environment name. If you want to force "linters" job to use python3.8 only under CI/CD, is impossible.
>
> Using basepython=pythonX.Y combined with ignore_basepython_conflict=False seems the only way to enforce version use, and it comes at the cost of not being flexible for developers (as they may not have the exact version that we want to use on CI jobs).
>
> While for unittest jobs we do use pyXY in the environment name, we do not have the same for "linters", "docs". Alternative to add `{pyXY}-linters` seems to be the only option to trick it.

Is there a reason you need a specific py3 version for these jobs?
Normally, at least in OpenStack, we just want these jobs to not use
py27. Which version of py3 is used to build docs is usually not as big
of a concern.

Sean




More information about the openstack-discuss mailing list