Skip to content

Conversation

@jamesobutler
Copy link
Collaborator

@jamesobutler jamesobutler commented Nov 13, 2025

Python 3.9 is now end-of-life as of 2025-10-31 (see https://endoflife.date/python). Whenever dicomweb-client last dropped python version support, the justification was because they were end-of-life versions as well (see #113).

I would recommend a v0.61.0 release considering the python requirements will have changed. Similarly in dicomweb-client v0.60.0 there was a bump in the python requirement.

Copy link
Collaborator

@CPBridge CPBridge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jamesobutler this all makes sense to me

@CPBridge
Copy link
Collaborator

CPBridge commented Nov 13, 2025

...although it looks like there are some fun new mypy problems to deal with following the mypy version bump

Python 3.9 is now end-of-life as of 2025-10-31 (see https://endoflife.date/python).
@jamesobutler jamesobutler changed the title Drop Python 3.9 support and begin using Python 3.14 in CI Drop Python 3.9 support Nov 13, 2025
@sonarqubecloud
Copy link

@jamesobutler
Copy link
Collaborator Author

@CPBridge Ok, I have limited this to just dropping Python 3.9 support and have a draft PR over at #123 to add testing for Python 3.14. That needs a mypy update that I'm working through.

Seeing the CI pass for the various Python version matrix is helpful in the context of myPR #120 for handling a pydicom deprecation issue.

@CPBridge CPBridge merged commit e1a8957 into ImagingDataCommons:master Nov 13, 2025
6 checks passed
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.

2 participants