Automatically manage python versions in tox environments

[ca-scribner]

Why it needs to get done

Because we strictly pin requirements, our tox unit and integration environments are particular about the python versions they're executed in. This requires devs and CI to execute tox -e unit, etc, in a particular python version

tox provides automated management for python version as part of an environment (for example, you can write a tox file that tests the same thing on multiple python versions) - we should use this to encapsulate the python version required into tox and avoid the developer from needing to change their python version

What needs to get done

Figure out how (and if) tox can be used to manage the python version for our tests, then implement this

When is the task considered done

• tox.ini files in all our charm repos are updated to manage python environments
• remove any references to python version that are no longer needed (for example, if a CI file previous set a specific python version)

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5053.

This message was autogenerated

[ca-scribner]

canonical/katib-operators#139 has additional discussion for this issue