Richard Laager via devel <devel@ntpsec.org>: > RHEL 6 support (measured in terms of security updates) ends in November > of this year. So by the time a version of NTPsec releases without Python > 2 support, we'd be looking at RHEL 7.
On top of that, it has been Red Hat's official position for some time that RHEL 6 shout *not* block transition to Python 3 only. There is some easy, officially endorsed workaround that I don't remember. Unfortunaly I can't find RH's statement about this; I'd recognize it if I saw it but web searches aren't turning it up. There may be other reasons to keep Python 2 support, but as Richard says RHEL 6 will stop being one of them before our next point release after this one. This is not a judgment I am making casually. Peter Donis and I wrote this: http://www.catb.org/esr/faqs/practical-python-porting/ It's still the best guide on how to write Python that runs under both 2 and 3. Peter and I have been tracking the transition very closely and one of the questions I'm keeping in my mind is when I amend that document to say "there is no longer any point in this for new code". That moment is nearly upon us, and I'm pretty certain it will arrive before 2020 ends. -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
