Thread priorities

[James Browning]

On 2025-03-04T20:00:13-0800, Hal Murray via devel wrote:
> Do we want to get a release out now or continue fixing/tweaking things?

The Internet recommends releasing early and often to improve engagement; we do 
neither.

===

On 2025-03-04T20:55:06-0800, Matt Selsky via devel wrote:
> - Are there any potential release blockers aside from
> https://gitlab.com/NTPsec/ntpsec/-/issues/830?

Is issue 830 a release blocker? Fedora wants it, but they are working around 
it now.

> - Are we OK with dropping python 2.6 support if needed for the waf upgrade?

As mentioned below, yes, I can get it working on 2.6, but we should drop the 
gratis support for it.

===

On 2025-03-04T21:37:19-0800, Hal Murray via devel wrote:
> Can we keep 2 copies of waf around?

Yes, I think we could. Fedora would probably be happy with changes to make 
waf-2.1 not break.

> Default to the new one, but publish a recipe for how to switch to the old
> one if you don't have Python3?

While bored (never a safe thing), I got it working on Python 2.6, which 
requires
- argparse from a site on the Internet
- a compatibility shim somewhere only Python 2.6 can find it.
- The below changes to wscript and wafhelpers/options.py

> Do we have to change any of our wscript or wafhelpers code?

TLDR: Upgrading to waf 2.1 requires several changes in wafhelpers/options.py
- Replacing quoted 'string' instances with bare str.
- Reworking handling of (un)defines, and (cross)(ld/c)flags

The latter change cascades into wscript needing more changes.

===

On 2025-03-05T01:33:17-0800, Hal Murray via devel wrote:
> Does new waf run on python 2.7?

Yes, it does. 2.6 even with the above compatibility shims.

-=*|*=-

.$\{PYTHONDIR2_6\}/sysconfig.py
[source,python]
----
from distutils.sysconfig import *

def get_path(*args, **kwargs):
    if ('purelib', 'posix_user', {'userbase': '/usr/local'}) == args:
           return '/usr/local/lib/python2.6/site-packages'
----

-30-