On 2025-03-04 23:37, Hal Murray via devel wrote:
matthew.sel...@twosigma.com said:
I sounds like we would want a release out before we start mucking with
threads given that your review of the code shows a lot of potential
complexity.
It's not so much the complexity as the time. We've been talking about a
release for a long time. How much longer do we want to wait?
- Are we OK with dropping python 2.6 support if needed for the waf upgrade?
A while ago, I suggested dropping support for 2.6 and got a lot of
pushback.
Did you?
Dropping support for 2.6 _and leaving support for 2.7_ is not the same
as dropping support for Python 2.x entirely.
I re-read the two threads. I don't see anyone objecting to removing 2.6.
I think the answer is at least "yes, we are OK with dropping python 2.6
support if needed for the waf upgrade". I think it is actually stronger,
at "we are okay with dropping python 2.6 support".
I think we should:
1) change "2, 6, 0" in pylib/wscript to "2, 7, 0".
2) in NEWS.adoc, add "* Python 2.7 is now the minimum supported version"
or "* Drop Python 2.6 support", whichever you prefer.
If you want to go further, then add a note to NEWS.adoc:
* This is likely to be the last release supporting Python 2.
That would put people on notice, without firmly committing to a timeline
for Python 2 removal.
--
Richard
_______________________________________________
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
