Skip to content

Conversation

@jacopoabramo
Copy link
Contributor

@jacopoabramo jacopoabramo commented Oct 6, 2025

Description

Closes #367 and #354

Motivation and Context

Python 3.9 reaches EOL end of this month; this is an attempt to mirror bluesky repo.

Currently blocked by #1959

How Has This Been Tested?

Tested locally but some changes due to autogenerating typed dictionary models are fishy.

@jacopoabramo jacopoabramo changed the title ENH: drop python 3.9 and support 3.13 ENH: drop python 3.8, 3.9 and support 3.13 Oct 6, 2025
- was used for python<3.9, which this PR should remove support for
@jacopoabramo
Copy link
Contributor Author

@evvaaaa any suggestions? Apparently some fields have been changed from NotRequired to Literal during the generation process (after setting the minimum python version to 3.10).

Copy link
Contributor

@evvaaaa evvaaaa left a comment

Choose a reason for hiding this comment

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

This would be nice, however, bluesky supports 3.9 still, and event-model is a required dependency. I wouldn't be happy updating this without also dropping 3.9 from bluesky.

@jacopoabramo
Copy link
Contributor Author

This would be nice, however, bluesky supports 3.9 still

There's a PR open for that. Once that's merged, this can be merged as well safely I believe

@jacopoabramo jacopoabramo requested a review from evvaaaa October 7, 2025 08:51
Copy link
Contributor

@evvaaaa evvaaaa left a comment

Choose a reason for hiding this comment

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

To be merged alongside the bluesky update.

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.

Drop Python 3.8/3.9 and add support for 3.13

2 participants