Skip to content

Conversation

@henryiii
Copy link
Collaborator

@henryiii henryiii commented Oct 8, 2025

We should be dropping 3.9 soon, but we still support 3.8. Let's drop that so a future version can drop 3.9. (For running, not targeting).

@henryiii henryiii force-pushed the henryiii/feat/drop38 branch 2 times, most recently from ec5ae9e to 8193d7f Compare October 10, 2025 14:16
Copy link
Collaborator

@theacodes theacodes left a comment

Choose a reason for hiding this comment

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

This looks good, but it looks like it caused our coverage to drop a tiny amount. Feel free to merge it once that's good.

Signed-off-by: Henry Schreiner <[email protected]>
@henryiii henryiii force-pushed the henryiii/feat/drop38 branch from f038a32 to 3833b51 Compare November 12, 2025 19:58
Signed-off-by: Henry Schreiner <[email protected]>
@henryiii henryiii force-pushed the henryiii/feat/drop38 branch from ba4274d to dae2162 Compare November 12, 2025 20:33
@henryiii
Copy link
Collaborator Author

I don't know why 3.8 was picking up subprocess calls, but 3.9+ wasn't. Anyway, we can use coverage's new(ish, a few months old) patch feature to enable this.

@henryiii henryiii merged commit e3afd2d into wntrblm:main Nov 12, 2025
18 checks passed
@henryiii henryiii deleted the henryiii/feat/drop38 branch November 12, 2025 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants