Yo Richard! On Mon, 4 Sep 2023 19:24:22 -0500 Richard Laager via devel <devel@ntpsec.org> wrote:
> Dropping support for Python 2 should allow for dropping most of the
> poly infrastructure. That code (pylib/poly.py) involves some
> contortions (see also [1]) to make it possible to run on both Python
> 2 and Python 3.
And it also makes Python 3 code way easier to write. Even when I
don't care about Python 2, I use the poly stuff.
> If we dropped support for Python 2, that should come in a couple
> phases. Phase 1 would be removing anything relating to Python 2
> itself. It should probably also include any changes relating to
> Python detection with waf. Phase 2 would be /carefully/ removing
> usage of the poly infrastructure, converting to idiomatic Python 3
> approaches. Once that is done, then we'd be rid of the 2 -> 3
> conversion baggage. These phases need not be separate releases, but
> should (IMHO) certainly be separate commits and likely be separate
> PRs.
A fair plan, and a lot of work, for little added value.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgpobBjBIjEeO.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
