You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the matrix tests run using Python 3.8. 3.8 is a sensible choice for ops and for 'infrastructure charms' that should support all the bases that currently supported Juju provides, but for 'application charms' it's reasonable to say that a more recent base (and therefore Python) is required.
Ideally, the matrix tests would be able to use either the base or a minimum Python version (e.g. in pyproject.toml) to determine which Python should be use for the compatibility test with the interface.
The text was updated successfully, but these errors were encountered:
in general, I think it'd be handy to start using uv to generate the venvs for the various interface tests. At the all packages for a test suite are installed in a fresh venv, but with the same python.
Currently, the matrix tests run using Python 3.8. 3.8 is a sensible choice for ops and for 'infrastructure charms' that should support all the bases that currently supported Juju provides, but for 'application charms' it's reasonable to say that a more recent base (and therefore Python) is required.
Ideally, the matrix tests would be able to use either the base or a minimum Python version (e.g. in pyproject.toml) to determine which Python should be use for the compatibility test with the interface.
The text was updated successfully, but these errors were encountered: