Skip to content

Conversation

@andrewdnolan
Copy link
Collaborator

No description provided.

@andrewdnolan andrewdnolan self-assigned this Oct 8, 2025
Copy link
Collaborator

@xylar xylar left a comment

Choose a reason for hiding this comment

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

@andrewdnolan , could you comment on the motivation to drop python 3.10? I don't think we were planning to drop it yet in polaris but we could if there's a reason to. pyproj might be such a reason.

@andrewdnolan
Copy link
Collaborator Author

@xylar No real motivation. I figured if we were adding support for python 3.14, we may as well cycle out 3.10. But, if polaris plans to support python 3.10 for a little while longer, than I'm happy to keep it for now.

@xylar
Copy link
Collaborator

xylar commented Oct 9, 2025

I agree, it would be tidier. We can discuss it.

I think it's good for packages with downstream dependencies to be a little cautious about dropping support because they kind of force it on their dependencies.

And python 3.14 support is still rolling out and hasn't reached mpas-tools yet. So polaris would be a bit squeezed at the moment.

@andrewdnolan andrewdnolan deleted the drop-python3.10-and-add-python3.14 branch October 13, 2025 20:40
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