Which Python version for new tool code?

[Joel Sherrill]

Hi

This situation seems to have changed with the release of RHEL 7.7. It now
includes Python 3.7 without having an addition repository per the
announcement.

https://www.zdnet.com/article/final-red-hat-enterprise-linux-7-version-released/


No idea when this will show up as a CentOS 7 upgrade. But this seems close
to
eliminating a barrier for moving to a newer Python.

--joel

On Mon, Aug 5, 2019 at 1:06 AM Chris Johns <chrisj at rtems.org> wrote:

> On 2/8/19 6:10 pm, Sebastian Huber 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?
> >
>
> As a general rule the widest range of versions the better but that sort of
> statement is easy to say and a pain to figure out. There needs to be
> compelling
> reason to have just python3 things that are not supported by `future`. Yes
> the
> clock is ticking for Py2 but a timely change means different things to
> different
> people.
>
> Importing a separate package is different. We cannot control what happens
> with
> that package however we can control if that specific tool is made
> available and
> installed. This means such a tool does not effect the other tools that may
> work.
>
> Chris
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190806/756dedc7/attachment-0002.html>