Skip to content

fix: declare in pyproject.toml too that we dropped py 3.9 - #85

Merged
dhdaines merged 3 commits into
mainfrom
dev.ej/drop-py39
Oct 29, 2026
Merged

dhdaines merged 3 commits into
mainfrom
dev.ej/drop-py39

Conversation

@joanise

@joanise joanise commented Oct 28, 2026

Copy link
Copy Markdown
Member

PR Goal?

One more small thing: if we're going to drop 3.9 from CI and cibuildwheels, we should declare that explicitly in pyproject.toml

Fixes?

an inconsistency

Priority?

before publishing 0.6.8

Confidence?

high

@joanise
joanise requested a review from dhdaines October 28, 2026 14:56

@dhdaines dhdaines left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Well, technically we still do support Python 3.9, but we can't verify it without tests, so I'm okay with this...

@dhdaines
dhdaines merged commit 2daf6e2 into main Oct 29, 2026
21 checks passed
@dhdaines
dhdaines deleted the dev.ej/drop-py39 branch October 29, 2026 00:47
@joanise

joanise commented Oct 29, 2026

Copy link
Copy Markdown
Member Author

Well, technically we still do support Python 3.9, but we can't verify it without tests, so I'm okay with this...

Yeah, it's going to keep working for a while, and then it won't and we won't notice it. I prefer forcing the use of <=0.6.7 with older Pythons, because we know for sure that that will work.

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