On Mar 18, 2025 13:44, Hal Murray via devel <devel@ntpsec.org> wrote:
> I tried to bisect the git. No luck. The issue depends on which Python I
> am running.
commit e899c2ffd4243e933150f2349874e4e462657c54
Author: James Browning <jamesb.f...@gmail.com>
Date: Thu Mar 13 02:06:11 2025 -0700
Use waf 2.1.4, revise, and drop Py2.6 builds.
Which python works the old way?
We now have two wafs.
lrwxrwxrwx 1 murray murray 9 Mar 13 02:24 waf -> waf-2.1.4
-rwxr-xr-x 1 murray murray 108317 Mar 13 02:24 waf-2.1.4
-rwxr-xr-x 1 murray murray 105631 Mar 13 02:24 waf-2.0.25
There is some magic that I don't know anything about that uses the old one
if you have an old python. Or something like that.
There is no magic, no fancy Python tricks. When you run waf or waf-2.1.4 you get new behavior. waf-2.0.25 gets you new behavior closer to the old behavior.
> I tried to bisect the git. No luck. The issue depends on which Python I
> am running.
commit e899c2ffd4243e933150f2349874e4e462657c54
Author: James Browning <jamesb.f...@gmail.com>
Date: Thu Mar 13 02:06:11 2025 -0700
Use waf 2.1.4, revise, and drop Py2.6 builds.
Which python works the old way?
We now have two wafs.
lrwxrwxrwx 1 murray murray 9 Mar 13 02:24 waf -> waf-2.1.4
-rwxr-xr-x 1 murray murray 108317 Mar 13 02:24 waf-2.1.4
-rwxr-xr-x 1 murray murray 105631 Mar 13 02:24 waf-2.0.25
There is some magic that I don't know anything about that uses the old one
if you have an old python. Or something like that.
There is no magic, no fancy Python tricks. When you run waf or waf-2.1.4 you get new behavior. waf-2.0.25 gets you new behavior closer to the old behavior.
_______________________________________________ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
