Skip to content

Review/python3.14 fixes - #38

Closed
aportagain wants to merge 11 commits into
upgrade/python3.14from
review/python3.14-fixes
Closed

aportagain wants to merge 11 commits into
upgrade/python3.14from
review/python3.14-fixes

Conversation

@aportagain

Copy link
Copy Markdown
Member

Hey Simon,

finally found time to look at your PR #37, thanks heaps, looks good overall!

I've made a few small changes, and then the main thing tried to support 3.11 to 3.14 for the dependency constraints, tox setup and tests... I know 3.11 is pretty old now, but might ease soft / partial upgrades of other operational stuff running 3.11, and I'd say is still in line with the ex-MetOcean CoP / guidelines / whatever ("For requires-python, set the lower bound as low as practical, as long as it doesn’t introduce issues. Realistically, supporting more than about four Python versions tends to become painful.", MOS CoP wiki page).

Have a look, maybe it makes sense, maybe I broke something else now... happy to chat next week or whenever you have time :)

Maybe just came from string search-and-replace?
Doesn't break anything, but maybe better this way to stay consistent
between the boo, int and float lists?
Wrong repo / package ;) Otherwise just says "WARNING: Failed to generate
report: No data to report."
Intentionally removed in a50fcc4, accidentally reintroduced in 4cf218d?
Funny colours on github.com, was also wrong in some of the older ones :)
From setup.py. If we decide to (still) keep both, we'd have to
specify setuptools as the build-system / build-backend... I think?
Just to be consistent with the one in pyproject.toml :)
Trying to support Python 3.11 to 3.14 results in different default time
resolutions (microsecond vs. nanosecond).
@aportagain

Copy link
Copy Markdown
Member Author

Oh, and GitHub-native PR "stacks" are new to me... didn't tick that box now, but feel free to change / use that if you think it makes sense... :)

@aportagain aportagain mentioned this pull request Sep 17, 2026
3 tasks done
@aportagain

Copy link
Copy Markdown
Member Author

I think Simon's now already made all the substantial changes in his corresponding PR / branch, so I'm gonna close this one.

@aportagain aportagain closed this Sep 20, 2026
@aportagain
aportagain deleted the review/python3.14-fixes branch September 20, 2026 23:29
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.

1 participant