Upgrade to Python 3.12
Merge request reports
Activity
added 23 commits
-
6bcc12a0...d4f10a70 - 19 commits from branch
develop - 7471f2b6 - Upgrade tabular code to pandas 2
- c186e972 - Bump pandas
- 1e11ba0a - py312
- 290a7175 - Test deps
Toggle commit list-
6bcc12a0...d4f10a70 - 19 commits from branch
added 10 commits
-
290a7175...f05052cc - 8 commits from branch
develop - 2a02a57d - py312
- 3d068535 - Update dependencies
-
290a7175...f05052cc - 8 commits from branch
assigned to @ahmil
requested review from @mscheidg
I think bumping the refs is fine. But should we really officially switch to 3.12. My argument is that a typical computer system will more likely have 3.11 by default than 3.12. A criteria could be that we wait for an actual release of 3.13 before switching (https://devguide.python.org/versions/). Would the new deps version work also on 3.11 in the setup script and in the Dockerfile?
The dependencies will work fine on 3.11 and 3.12.
I think most devs had to download py3.11 for the recent upgrade so I imagine they'd be proficient in making another bump. And python3.13 release candidate is already out and the official version will be out in a month. We can wait too though.
added 78 commits
-
eb37b4c8...80250fe3 - 75 commits from branch
develop - 7cd323f3 - py312
- f7e6fca0 - Update dependencies
- 11c462df - Update docs
Toggle commit list-
eb37b4c8...80250fe3 - 75 commits from branch
added 108 commits
-
ef3c8d06...23d733f9 - 105 commits from branch
develop - a02986bc - py312
- 76dddbd0 - Update docs
- 7744f1b2 - Monomock fix
Toggle commit list-
ef3c8d06...23d733f9 - 105 commits from branch
mentioned in commit 9a92e6f9