Skip to content

Conversation

@brownbaerchen
Copy link
Contributor

According to the status of Python versions, Python 3.13 is supported at least to some extend. When I last installed a fresh pySDC environment without explicitly specifying a Python version, I even ended up with 3.13. Therefore, I suggest we better test it to accommodate future users.
However, the pipeline is already too large as is, with some project tests taking a very long time. Therefore, I did not add 3.13 to those tests. In fact, I would be open to stop doing the project tests with all supported Python versions. IMHO, it would suffice to use the latest version (only 3.13 in this case) or to allow projects to specify a supported Python version.

@pancetta
Copy link
Member

Let's kick 3.9.

@tlunet
Copy link
Member

tlunet commented Jun 10, 2025

+1 on the project tests for one Python version only.

Also, using the latest version for project test should simplify maintaining on the long term IMO => once a year, we upgrade the latest version, and eventually correct the projects that need adaptation. Just need a proper clarification on when we upgrade every year.

@pancetta
Copy link
Member

Fine by me. Projects should have a way to specify their (set of) Python versions that should be tested. pySDC's core should be tested against as much as we can, though.

@tlunet
Copy link
Member

tlunet commented Jun 10, 2025

Fine by me. Projects should have a way to specify their (set of) Python versions that should be tested. pySDC's core should be tested against as much as we can, though.

But what about when a project required some python versions that are not supported anymore ?

@pancetta
Copy link
Member

You mean like, 3.8? If this project cannot be updated to support a newer version and if porting will be to tedious, we have to move it to deprecated. Not sure what else we can do?

@pancetta
Copy link
Member

But then, what's the harm? if the core of pySDC still works with that version? The more the better, no?

@brownbaerchen
Copy link
Contributor Author

It's straightforward to set the Python version individually by simply adding - python=3.13 to the environment files.

However, why not treat the Python version like any other dependency? If we don't specify a version, micromamba will select the latest reasonable version. Then we either support the latest that users get, or we react once the pipeline fails for some reason and restrict to an older version.

In any case, I suggest we don't remove 3.9 from the core tests because it is still supported.

@pancetta
Copy link
Member

Fine by me. Wild, but fine.

@brownbaerchen
Copy link
Contributor Author

Let's get this merged!

@pancetta pancetta merged commit c5fbd09 into Parallel-in-Time:master Jun 17, 2025
47 checks passed
brownbaerchen added a commit to brownbaerchen/pySDC that referenced this pull request Jun 17, 2025
* Add testing for Python 3.13 to pipeline

* Try removing mpi4py restriction

* Test

* Testing projects with latest Python version only
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.

3 participants