-
Notifications
You must be signed in to change notification settings - Fork 8
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
Move to Python 3.10 #2132
Labels
Milestone
Comments
jim-sheldon
added
the
P1: Launch blocker
Needs fixing before we launch, schedule some time to investigate & fix
label
Aug 30, 2021
Data export still uses Lambda, aside from that, everything else can move to 3.9 |
Lambda now supports Python 3.9! https://aws.amazon.com/about-aws/whats-new/2021/08/aws-lambda-adds-support-python-3-9/ |
abhidg
added a commit
that referenced
this issue
Nov 5, 2021
abhidg
added a commit
that referenced
this issue
Nov 7, 2021
abhidg
added a commit
that referenced
this issue
Nov 8, 2021
iamleeg
pushed a commit
that referenced
this issue
Nov 12, 2021
abhidg
added a commit
that referenced
this issue
Oct 17, 2022
abhidg
added a commit
that referenced
this issue
Oct 17, 2022
abhidg
added a commit
that referenced
this issue
Oct 19, 2022
abhidg
added a commit
that referenced
this issue
Oct 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We don't need to limit ourselves to 3.8 anymore, as we don't run parsers on AWS Lambda, which did not support more up-to-date Python environments. This should also make moving to 3.10 easier; it should release on October 4.
The text was updated successfully, but these errors were encountered: