Update dependency python

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
python	uses-with	minor	3.11.x -> 3.13.x
python	final	minor	3.11 -> 3.13

---

Release Notes

actions/python-versions (python)

v3.13.2: 3.13.2

Compare Source

Python 3.13.2

v3.13.1: 3.13.1

Compare Source

Python 3.13.1

v3.13.0: 3.13.0

Compare Source

Python 3.13.0

v3.12.9: 3.12.9

Compare Source

Python 3.12.9

v3.12.8: 3.12.8

Compare Source

Python 3.12.8

v3.12.7: 3.12.7

Compare Source

Python 3.12.7

v3.12.6: 3.12.6

Compare Source

Python 3.12.6

v3.12.5: 3.12.5

Compare Source

Python 3.12.5

v3.12.4: 3.12.4

Compare Source

Python 3.12.4

v3.12.3: 3.12.3

Compare Source

Python 3.12.3

v3.12.2: 3.12.2

Compare Source

Python 3.12.2

v3.12.1: 3.12.1

Compare Source

Python 3.12.1

v3.12.0: 3.12.0

Compare Source

Python 3.12.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[webbnh]

I suspect that the unit tests are failing due to a bottle update.

[dbutenhof]

I suspect that the unit tests are failing due to a bottle update.

Is the failure coincidental because of an update in bottle, or is this directly related to the Python 3.13 update? (Which seems ... aggressive, since we're mostly still using 3.10 or even 3.9 ... but maybe not.)

[webbnh]

The bot thinks that we should be using the "current" version of Python for our base image (hence this PR). Opening the PR triggered a CI run which installed a fresh version of the dependencies, which includes the "current" version of bottle, which, apparently, has the same incompatibility as Pbench faced. And, so, the unit tests failed.

I don't think this has anything to do with Python 3.13. I think it's all about bottle and how we use it. Since we're not rev-locking our dependency on bottle, I guess there was no need for the bot to propose an update to it, so we didn't notice the problem until a different update came by and prompted us to rebuild.

At this time, I'm not particularly excited about updating Python. We probably should make a change here to address the bottle problem, one way or another, though. But, I'm not feeling particularly motivated to do that, right now, either. So, I made my comment above as a note to a future reader (who might well be me...), and I figured I would leave the PR open until we feel like dealing with it.