Initial GitHub workflow testing for Debian 13 #2477
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Looks like Pillow 10.3.0 doesn’t support Python 3.13. |
tompollard
added a commit
that referenced
this pull request
Aug 28, 2025
Bumps Pillow. Now supports Python 3.13 so may help with #2477.
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 4, 2025
Bumps [Pillow](https://github.com/python-pillow/Pillow) from 10.3.0 to 11.3.0. Release notes at: https://pillow.readthedocs.io/en/stable/releasenotes/11.3.0.html Pillow 11.3.0 supports Python 3.13 so this update may help with #2477.
Member
|
@bemoody please could you rebase this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test compatibility with Debian 13, by running the
physionet-upgrade-testworkflow on adebian:13container.This is a preliminary test, and I'm not proposing to change all of the scripts and GitHub workflows yet, because it'll probably be another couple of months before PhysioNet gets around to upgrading. No point in running an excessive number of workflows in the meantime.