Skip to content

Conversation

@agoscinski
Copy link
Collaborator

@agoscinski agoscinski commented Jun 27, 2025

Our code fails for <py3.12. Somehow hatch runs on different python version. I don't know where it finds executable from. But see the CI from latest run on main for py3.11
image

I needed to add to the test matrix more versions and changed the default to use system python version. The fixes that need to be done in the code are marginal.

strategy:
matrix:
python-version: ['3.10', '3.11', '3.12', '3.13']
python-version: ['3.11']
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be reverted

pyproject.toml Outdated
[tool.hatch.envs.default]
installer = "uv"
python = "3.12"
python = "python"
Copy link
Collaborator

@GeigerJ2 GeigerJ2 Jul 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix this to something static. 3.10 ? 3.12 ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we agreed to use py3.12

Due to the hatch setup the tests in the CI only ran on py312. It seems
that hatch python discoverability detected a py312 version on the runner
and therefore always defaulted to py312.

It is needed to add to the python version to the test matrix to support
the other python versions for running with hatch test.
@agoscinski agoscinski changed the title Fix testing for < py3.12 Enable testing for py310 py311 and py313 in CI Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants