[U-Boot] [RFC] Minimum Python 3 version?
Hey all,
I'm currently kicking test.py to use Python 3 instead of Python 2.7 and seeing places where it would (seemingly) be nice to be able to say that we have Python 3.6 as our minimum version. To do this however we'll have to tell people using older LTS distributions that they need to figure out the best way for them to install a newer Python is, if they want to run tests at least.
This will also mean moving GitLab to "bionic" rather than "xenial", but that's not too bad and I've done so for trying to get all of the fs tests to run (they don't, but I think that's down to needing to kick gitlab-runner harder) and also moving Travis-CI to bionic but that too is now just a few-line change to .travis.yml
So, does anyone object to saying that for everything that uses Python to work, Python 3.6 or newer is needed, and for more common tools we'll make best-effort to support older?
I'm currently kicking test.py to use Python 3 instead of Python 2.7 and seeing places where it would (seemingly) be nice to be able to say that we have Python 3.6 as our minimum version. To do this however we'll have to tell people using older LTS distributions that they need to figure out the best way for them to install a newer Python is, if they want to run tests at least.
This will also mean moving GitLab to "bionic" rather than "xenial", but that's not too bad and I've done so for trying to get all of the fs tests to run (they don't, but I think that's down to needing to kick gitlab-runner harder) and also moving Travis-CI to bionic but that too is now just a few-line change to .travis.yml
So, does anyone object to saying that for everything that uses Python to work, Python 3.6 or newer is needed, and for more common tools we'll make best-effort to support older?
That makes sense to me, the el8 distros (RHEL, CentOS etc) have 3.6 and el7 has 3.6 available by means, Fedora is at least 3.6 everywhere for current releases so I don't think we should have any issues.
Peter
On 9/27/19 6:36 PM, Peter Robinson wrote:
I'm currently kicking test.py to use Python 3 instead of Python 2.7 and seeing places where it would (seemingly) be nice to be able to say that we have Python 3.6 as our minimum version. To do this however we'll have to tell people using older LTS distributions that they need to figure out the best way for them to install a newer Python is, if they want to run tests at least.
This will also mean moving GitLab to "bionic" rather than "xenial", but that's not too bad and I've done so for trying to get all of the fs tests to run (they don't, but I think that's down to needing to kick gitlab-runner harder) and also moving Travis-CI to bionic but that too is now just a few-line change to .travis.yml
So, does anyone object to saying that for everything that uses Python to work, Python 3.6 or newer is needed, and for more common tools we'll make best-effort to support older?
That makes sense to me, the el8 distros (RHEL, CentOS etc) have 3.6 and el7 has 3.6 available by means, Fedora is at least 3.6 everywhere for current releases so I don't think we should have any issues.
Debian Stretch has Python 3.4.2. End of life in 2020, end of long term support in 2022
Debian Buster has Python 3.7.3 End of life in 2022.
I would not expect expect Debian Stretch moving to current U-Boot. So requiring Python 3.6 to build current U-Boot seems ok for Debian.
Best regards
Heinrich
On 2019-09-27, Heinrich Schuchardt wrote:
On 9/27/19 6:36 PM, Peter Robinson wrote:
I'm currently kicking test.py to use Python 3 instead of Python 2.7 and seeing places where it would (seemingly) be nice to be able to say that we have Python 3.6 as our minimum version. To do this however we'll have to tell people using older LTS distributions that they need to figure out the best way for them to install a newer Python is, if they want to run tests at least.
...
So, does anyone object to saying that for everything that uses Python to work, Python 3.6 or newer is needed, and for more common tools we'll make best-effort to support older?
That makes sense to me, the el8 distros (RHEL, CentOS etc) have 3.6 and el7 has 3.6 available by means, Fedora is at least 3.6 everywhere for current releases so I don't think we should have any issues.
Debian Stretch has Python 3.4.2. End of life in 2020, end of long term support in 2022
Debian Buster has Python 3.7.3 End of life in 2022.
I would not expect expect Debian Stretch moving to current U-Boot. So requiring Python 3.6 to build current U-Boot seems ok for Debian.
Python 3.6+ seems good to me, yes. Not planning on backporting anything new to older Debian releases.
Thanks for working on the update to python3!
live well, vagrant
On 27/09/2019 18:05, Tom Rini wrote:
Hey all,
I'm currently kicking test.py to use Python 3 instead of Python 2.7 and seeing places where it would (seemingly) be nice to be able to say that we have Python 3.6 as our minimum version. To do this however we'll have to tell people using older LTS distributions that they need to figure out the best way for them to install a newer Python is, if they want to run tests at least.
This will also mean moving GitLab to "bionic" rather than "xenial", but that's not too bad and I've done so for trying to get all of the fs tests to run (they don't, but I think that's down to needing to kick gitlab-runner harder) and also moving Travis-CI to bionic but that too is now just a few-line change to .travis.yml
So, does anyone object to saying that for everything that uses Python to work, Python 3.6 or newer is needed, and for more common tools we'll make best-effort to support older?
I just checked openSUSE in that regard and we should be fine. The oldest version, openSUSE Leap 15.0 provides python 3.6.5
Thanks for working on that! Matthias
participants (5)
-
Heinrich Schuchardt -
Matthias Brugger -
Peter Robinson -
Tom Rini -
Vagrant Cascadian