Skip to contentSkip to conversation

Minimum Python 3 version?

RFC Tom Rini 5 participants 5 messages Sep 27, 2019 – Oct 1, 2019

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

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?

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190927/0632d7a2/attachment.sig>
#1 lore raw
Quoted 14 lines

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

Quoted 3 lines

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

#2 lore raw
Quoted 14 lines · Peter Robinson
Quoted 14 lines

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

Quoted 7 lines
Quoted 3 lines

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

#3 lore raw
Quoted 7 lines · Heinrich Schuchardt
Quoted 6 lines · Peter Robinson
Quoted 6 lines

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.

...

Quoted 8 lines
Quoted 7 lines
Quoted 3 lines

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.

Quoted 8 lines

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190927/5256401c/attachment.sig>

#4 lore raw
In reply to Tom Rini
Quoted 15 lines · Tom Rini

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

Quoted 4 lines

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191001/aa42a009/attachment.sig>