Python version in CI resolves to latest patch (e.g., 3.10.18) – possible compatibility gap for users

[SermetPekin]

Hi @LarsKue,

I noticed the workflow uses python-version: 3.10, which resolves to the latest patch (like 3.10.18). This might be newer than what some users have locally (e.g., 3.10.0).

Just wanted to mention that testing only on the latest patch could miss issues for users on older 3.10.x versions. Would it be feasible to also test with the earliest patch (such as 3.10.0), which would be more in line with what’s specified in the toml file?

Thanks for considering!
GH test resolves to 3.10.18
GH Actions

[LarsKue]

Can you clarify how it would align more closely with the pyproject.toml? In both the workflow and the requirements, the dependency is specified as 3.10. In general, I don't think this should be a big issue, since it is only a patch-level version difference. I think having the workflows run faster is preferable then.

[SermetPekin]

What I mean is since toml file specifies 3.10 then when a user has lets say 3.10.0 (or 3.10.8 in my case) bayesflow does not warn user to use a later version of python. On the other hand on the Workflow (CI Test yaml file) specifies 3.10 but it is only testing with 3.10.18 as it is in the workflow of this project GH Actions which actually is testing a later version than some users' version and it is getting harder to test their use cases. In other words Github actions when we do not specify a patch (when we say 3.10) apparently tests with a latest version of that major such as 3.10.18

[LarsKue]

Thank you for clarifying and for raising the issue. I agree that there is a certain discrepancy between what we test and what users may have on their machine. However, having loose version requirements is usually beneficial for users that want to also install other packages (i.e., most users).

This leaves us with the dilemma that we cannot reasonably test every patch of every dependency, but we also do not want to restrict our dependency tree to a single patch.

I unfortunately do not see a solution to this without significantly blowing up our GitHub Actions quota. However, I am definitely open to suggestions.

[SermetPekin]

My suggestion is to specify 3.10.0 instead of 3.10 on test.yaml file :)

[SermetPekin]

I understand that the purpose (and the tradition is to test the earliest version) and I assume by specifying 3.10 on CI (tests.yaml) file we actually already hoping that it would test with 3.10.0 bu apparently GH Actions chooses something else for us. Maybe we can be more specific by saying with 3.10.0 on this yaml file if we are not intended to test only on 3.10.18. I think that would make no difference in the number of tests on our actions. instead of 3.10.18 I am suggesting testing with 3.10.0 and on yaml file if we change just one line as 3.10.0 (I can check) that would solve the problem I guess.