-
Notifications
You must be signed in to change notification settings - Fork 137
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
Update Python dependency to 3.9 #2691
Comments
Our TW target has already been relying on Py3.8 for the last couple of releases given there was no Py3.6 available, see: |
Note that we have a now created and linked partner issue in our rockstor-rpmbuild repo: |
With the following: which would be enacted by our rpm spec in linked issue:
we have:
Where-as these are available in default Tumbleweed. |
With reference to the last comment, we do however have a Py3.9 available in our default Leap 15.5 repos: Py3.8 Leap 15.5:
Py3.9 Leap 15.5:
So given the difficulty involved (read blocker) of adding say a devel language repo, we might look to instead jump to Py3.9 across the board. |
Re our testing branch current Django version of 2.2.28 we have the following Python version limits:
So all good on Py3.9, but no further! Assessing our current OS targets for Py3.9.Leap 15.4N.B. from: https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.4 TWHas Py3.8 & Py3.9 of both packages. |
Leap 15.5 dev setup.
|
Our current .venv appears to be still locked to a Py3.6 reference:
however we saw something similar in our early testing channel and so we can assume that the rpm update will wipe .venv and reinstate it as per: So we can assume our RPM update will do the following via scriptlet entries:
|
Proof of concept (Leap 15.5 dev base)With to-be-linked project.py changes to date:
|
Update from Py3.6 to Py3.9 as commonly available in default repos across our Leap 15.4/15.5/TW 'Built on ...' OS targets.
Emulating an rpm update for now we have, under a Py3.9:
Fancy that. I suspect we have left our gunicorn version in the dust here so will likely have to chase that up in a follow-up issue of it's own.
|
…-to-3.9 Update Python dependency to 3.9 #2691
Closing as: |
To date, in the current testing channel, we have used Py3.6. However, even thought this is our upstream OS (bar TW) default it is EOL and constraining our options. With TW no longer providing even Py3.6. Ergo move to
Py3.8Py3.9 EDIT see comment: across all our OS targets by way of the smallest step available to us across our target OSs, as we work out the ramifications of this and some of our existing older dependencies.The text was updated successfully, but these errors were encountered: