Yo Fred!
On Tue, 4 Feb 2025 14:55:30 -0800 (PST)
Fred Wright via devel wrote:
> If you refactor the
> underlying code to conform to the Python 3 philosophy of treating
> text and binary data as different data types, then you have code that
> works in Python 3 *and Python 2* without the wrappers.
On Tue, 4 Feb 2025, Richard Laager via devel wrote:
On 2025-02-03 23:31, Hal Murray via devel wrote:
Did you see my comment about how dropping Python 2 before getting rid of
the polyXXX wrapers is dangerous, because removing the wrappers without
properly fixing the underlying code is more like
On 2025-02-03 23:31, Hal Murray via devel wrote:
Did you see my comment about how dropping Python 2 before getting rid of
the polyXXX wrapers is dangerous, because removing the wrappers without
properly fixing the underlying code is more likely to break Python 3 than
Python 2?
I'm concerned t
> Did you see my comment about how dropping Python 2 before getting rid of
> the polyXXX wrapers is dangerous, because removing the wrappers without
> properly fixing the underlying code is more likely to break Python 3 than
> Python 2?
Yes, but I don't know enough about Python to know what it
On Mon, 3 Feb 2025, Hal Murray via devel wrote:
Uh, yes. I'll continue to object. It buys us nothing now, and it will
annoy some people. Maybe later this year.
OK. I guess I missed your previous objections.
Have we actually made contact with anybody using python2 (and NTPsec)?
Should w
Yo Hal!
On Mon, 03 Feb 2025 20:08:46 -0800
Hal Murray wrote:
> > Uh, yes. I'll continue to object. It buys us nothing now, and it
> > will annoy some people. Maybe later this year.
>
> OK. I guess I missed your previous objections.
>
> Have we actually made contact with anybody using py
> Uh, yes. I'll continue to object. It buys us nothing now, and it will
> annoy some people. Maybe later this year.
OK. I guess I missed your previous objections.
Have we actually made contact with anybody using python2 (and NTPsec)?
Should we put a note in NEWS saying this is the last re
Yo Hal!
On Fri, 31 Jan 2025 16:14:07 -0800
Hal Murray via devel wrote:
> I think we should drop support for python 2 before this release. Any
> objections?
Uh, yes. I'll continue to object. It buys us nothing now, and it
will annoy some people. Maybe later this year.
RGDS
GARY
---
There are a lot of merge requests in the queue. I approved a few without
as much checking as I would like to do. I expect to do more of the same,
so git master may be unstable for a while.
We will have to do a lot of testing before the actual release.
For now, I've gotten side tracked on fi
Yo Hal!
On Sun, 07 Jan 2018 19:22:30 -0800
Hal Murray wrote:
> >> I don't think running directly out of the source tree is very
> >> interesting.
>
> > OTOH, a bunch of programs, like ntplogtemp, that used to be able to
> > run in tree, no longer can. I think that is our loss. Creeping
> >
Yo Richard!
On Sun, 7 Jan 2018 23:03:41 -0600
Richard Laager via devel wrote:
> I did some light looking at eselect, and it seems it uses various
> mechanisms under the hood to implement the selection, depending on the
> situation.
Yeah, 'various'. More than I can keep track of. But the comma
On 01/07/2018 08:53 PM, Gary E. Miller via devel wrote:
> On Sun, 7 Jan 2018 18:02:32 -0600
> Richard Laager via devel wrote:
>
>> Debian has two versions of Python. Debian's Python 3.x executable name
>> is python3, so `/usr/bin/env python` gets me Python 2.x. I think this
>> is a great example
>> I don't think running directly out of the source tree is very
>> interesting.
> OTOH, a bunch of programs, like ntplogtemp, that used to be able to run
> in tree, no longer can. I think that is our loss. Creeping complexity
> for no real user benefit.
Sometimes life is tough.
python ntpclie
Yo Hal!
On Sun, 07 Jan 2018 16:41:16 -0800
Hal Murray via devel wrote:
> I don't think running directly out of the source tree is very
> interesting.
OTOH, a bunch of programs, like ntplogtemp, that used to be able to run
in tree, no longer can. I think that is our loss. Creeping complexity
f
Yo Richard!
On Sun, 7 Jan 2018 18:02:32 -0600
Richard Laager via devel wrote:
> Debian has two versions of Python. Debian's Python 3.x executable name
> is python3, so `/usr/bin/env python` gets me Python 2.x. I think this
> is a great example of this question.
Just two python's? Right now Gen
rlaa...@wiktel.com said:
[Running with Python3]
Thanks.
> That way, the scripts can be run directly from the source tree (with the /
> usr/bin/env shebang).
I don't think running directly out of the source tree is very interesting.
Many of the python programs need our python libraries and one
Debian has two versions of Python. Debian's Python 3.x executable name
is python3, so `/usr/bin/env python` gets me Python 2.x. I think this is
a great example of this question.
My previous rough sketch hand-waved over a complicated part, which is
how to figure out the python binary path. Even if
Yo Richard!
On Sun, 7 Jan 2018 16:27:11 -0600
Richard Laager via devel wrote:
> On 01/07/2018 04:27 AM, Hal Murray via devel wrote:
> > Is there a recipe for setting our stuff up to use Python3 when the
> > system defaults python to Python2?
Depends a lot on what OS you are using. On gentoo
On 01/07/2018 04:27 AM, Hal Murray via devel wrote:
> Is there a recipe for setting our stuff up to use Python3 when the system
> defaults python to Python2?
For the Debian packaging, I do two things:
1) Instead of ./waf configure/build/install, I use: python3 waf ...
2) I patch the #!/usr/bin/e
I just pushed lots of documentation updates, mostly in the crypto area.
(No thumbs up/down message from the autobuild stuff yet. I guess it's
sleeping.)
There is (much?) more work to do.
I'm going to take a break from documentation for a while.
There is a new hack in attic/digest.c
It works on
I've been distracted the last couple of days by trying to spin up
another ICEI project that's on a tight deadline. It seems I missed
replying on a couple of threads. This is my attempt to carch up.
Hal Murray:
>How important is supporting gpsd on systems without SHM?
Realistically, not very.
W
Hal Murray via devel :
> Eric:
> I don't understand the python finding libraries area. It seems reasonable
> to ask hackers and developers to add a PYTHONPATH to their environment. It
> seems non-good to me to ask every sysadmin to hack their root environment.
I ruefully agree. Unfortunatel
I think I fixed the iburst startup problems.
I also added tests/time-startup.sh which is a script I used for timing. It
includes
export PYTHONPATH=/usr/local/lib/python2.7/site-packages
because that was the quickest way to get it working on my system.
Eric:
I don't understand the python fi
23 matches
Mail list logo
