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

Python 3.8 EOL looms #1916

Open
dsweber2 opened this issue Dec 15, 2023 · 3 comments
Open

Python 3.8 EOL looms #1916

dsweber2 opened this issue Dec 15, 2023 · 3 comments
Labels
future-solution Solutions to problems we don't have yet but still dread

Comments

@dsweber2
Copy link
Contributor

Came up in discussions with @nolangormley, it appears 3.8 is EOL by the end of 2024. There are some packages which seem to depend on 3.8, so we need to figure out how to update that/workaround. Related to #1854

@dsweber2 dsweber2 added the future-solution Solutions to problems we don't have yet but still dread label Dec 15, 2023
@melange396
Copy link
Contributor

looking at the version release cycle info in your python.org link, we might want to aim to use python 3.12 for longevity, but we could end up being hamstrung into bumping to just 3.9 instead as seen in cmu-delphi/delphi-epidata#1019

@dshemetov
Copy link
Contributor

Some useful resources:

@dshemetov
Copy link
Contributor

Some criteria:

  • upgraded Python version should support all our dependencies
  • upgraded Python version should be supported by our Dockerfiles (or we need to find workarounds for those Dockerfiles)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future-solution Solutions to problems we don't have yet but still dread
Projects
None yet
Development

No branches or pull requests

3 participants