Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop Python 3.9 support? #374

Open
ElliottKasoar opened this issue Jan 3, 2025 · 0 comments · May be fixed by #377
Open

Drop Python 3.9 support? #374

ElliottKasoar opened this issue Jan 3, 2025 · 0 comments · May be fixed by #377
Assignees
Labels
question Further information is requested

Comments

@ElliottKasoar
Copy link
Member

This has been discussed at various stages (e.g. #303, #312, #328, #372), but at some point we will drop support for Python 3.9.

My general feeling was to roughly stick to the Python release cycle, or at least wait until we can properly support 3.13, but some packages (roughly) follow NEP29, which has already dropped 3.9.

In particular, this seems to be the case for Materials Project packages e.g. pymatgen, and projects which interact with it e.g. CHGNet.

It's worth noting that PyTorch decided against dropping 3.9 yet, but perhaps more practically, the question is how much we lose from dropping support now? My impression is that most HPC users are required to to install a new version of Python anyway, and I would imagine locally using a different version is less of an issue.

The issue discussed in #347 may also be fixable.

@ElliottKasoar ElliottKasoar added the question Further information is requested label Jan 3, 2025
@ElliottKasoar ElliottKasoar self-assigned this Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant