Which Python version for new tool code?

Sebastian Huber sebastian.huber at embedded-brains.de
Fri Aug 2 15:28:25 UTC 2019


----- Am 2. Aug 2019 um 15:52 schrieb joel joel at rtems.org:

> On Fri, Aug 2, 2019 at 8:21 AM Sebastian Huber <
> sebastian.huber at embedded-brains.de> wrote:
> 
>> On 02/08/2019 15:14, Joel Sherrill wrote:
>> >
>> > On Fri, Aug 2, 2019 at 3:10 AM Sebastian Huber
>> > <sebastian.huber at embedded-brains.de
>> > <mailto:sebastian.huber at embedded-brains.de>> wrote:
>> >
>> >     Hello,
>> >
>> >     the EOL of Python 2.7 is soon, so it will be Python 3 for sure:
>> >
>> >     https://pythonclock.org/
>> >
>> >     The EOL of Python 3.4 was March 18, 2019:
>> >
>> >     https://www.python.org/downloads/release/python-3410/
>> >
>> >     Is it all right to start with Python 3.5?
>> >
>> >
>> > Sadly, not if we intend to support RHEL 7 until it hits EOL.
>> >
>> > https://access.redhat.com/support/policy/updates/errata
>> >
>> > That's still the standard Linux in all the big organizations in the US.
>> >
>> > $ python --version
>> > Python 2.7.5
>>
>> Which Python 3 do they ship?
>>
> 
> As best I can tell, no official repository includes Python 3. There are
> un-official addon repos
> with Python 3.
> 
> The users who are using RHEL 7 are unlikely to allow those repos to be used.

Puh, this is a bit unexpected. So at least everything related to the build system must be Python 2.7 compatible.

Doorstop requires Python 3.5:

https://github.com/jacebrowning/doorstop#requirements


More information about the devel mailing list