-
Notifications
You must be signed in to change notification settings - Fork 284
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
What are the implications of adopting NEP29? #4369
Comments
Communication:
|
@jamesp Should this be converted into a discussion? |
There is a discussion for this: #4332. This list of actions was written at the end of our peloton on 2021-10-13 to capture the specific actions we would like to address before adopting NEP29. If an item requires substantial work the list could be refined into individual issue items by those who would like to tackle them. |
Python core dependency views on NEP29: Doing it:
No indication from a fairly quick google:
|
Thanks @wjbenfold, first item on the list ticked off! |
Yes
No |
My reading of this
is that we should be supporting all python versions newer than python3.7*. So getting the tests working with 3.9 and 3.10 should be priority. *Since our anticipated release date for Iris3.2 is January (#4129) python3.7 will have fallen out of the 42 month window by release. |
The text was updated successfully, but these errors were encountered: