Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Matthew Selsky via devel : > Eric, didn't you file a ticket with waf > (https://github.com/waf-project/waf/issues/1897) for this same issue in > January 2017? That's clearly the same functional issue, but at the time I did not yet have any idea that waf itself was (even partly) the victim of an

Re: Python Library Cleanups

2017-09-26 Thread Matthew Selsky via devel
On Tue, Sep 26, 2017 at 07:30:02PM -0400, Eric S. Raymond via devel wrote: > Gary E. Miller via devel : > > > 2. Gary files a bug upstream to the Python devs detailing how > > > get_python_lib() is implicated in FHS nonconformance. Gary, you > > > willing? > > > > I'm feeling like a broken record.

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Fred Wright via devel : > > On Tue, 26 Sep 2017, Eric S. Raymond wrote: > > Fred Wright via devel : > > > > > BTW, I have a tool that lists a few things including the library paths for > > > every version of Python it can find on the system. I can submit it to > > > devel/ if you like. > > > > Pl

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Gary E. Miller via devel : > > 2. Gary files a bug upstream to the Python devs detailing how > > get_python_lib() is implicated in FHS nonconformance. Gary, you > > willing? > > I'm feeling like a broken record. The current behavior is a feature, > not a bug. You know I love to bash Python, but

Re: Python Library Cleanups

2017-09-26 Thread Fred Wright via devel
On Tue, 26 Sep 2017, Eric S. Raymond wrote: > Fred Wright via devel : > > > BTW, I have a tool that lists a few things including the library paths for > > every version of Python it can find on the system. I can submit it to > > devel/ if you like. > > Please do. MR submitted. Fred Wright _

Re: Python Library Cleanups

2017-09-26 Thread Gary E. Miller via devel
Yo Eric! On Tue, 26 Sep 2017 18:55:31 -0400 "Eric S. Raymond via devel" wrote: > > > Does this means the FHS nonconformance isc an upstream bug? > > > > Exactly. And one that nobody bothered to complain about for GPSD. > > Well, *that* changes things a lot. > > 2. Gary files a bug upstre

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Fred Wright via devel : > > On Tue, 26 Sep 2017, Eric S. Raymond wrote: > > Fred Wright via devel : > > > > Not Gentoo, the FHS. And the package I am using is git head. > > > > > > The point is that the portable way to determine where to install the > > > libraries is to ask Python via the get_py

Re: Python Library Cleanups

2017-09-26 Thread Gary E. Miller via devel
Yo Fred! On Tue, 26 Sep 2017 15:16:50 -0700 (PDT) Fred Wright via devel wrote: > On Tue, 26 Sep 2017, Eric S. Raymond wrote: > > Fred Wright via devel : > > > > Not Gentoo, the FHS. And the package I am using is git head. > > > > > > The point is that the portable way to determine where to

Re: Python Library Cleanups

2017-09-26 Thread Fred Wright via devel
On Tue, 26 Sep 2017, Eric S. Raymond wrote: > Fred Wright via devel : > > > Not Gentoo, the FHS. And the package I am using is git head. > > > > The point is that the portable way to determine where to install the > > libraries is to ask Python via the get_python_lib() function. Whatever it > >

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Gary E. Miller via devel : > Locally installed user source is supposed to go in /usr/local/. > > System packages are supposed to go in /usr/ > > Not obeying the 30 year old convention of wchich to pick is bad. But > the new patches put some in /usr and some in /usr/local/which is just > wrong.

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Fred Wright via devel : > > Not Gentoo, the FHS. And the package I am using is git head. > > The point is that the portable way to determine where to install the > libraries is to ask Python via the get_python_lib() function. Whatever it > returns (as long as you don't supply the 'prefix' argume

Re: Python Library Cleanups

2017-09-26 Thread Gary E. Miller via devel
Yo Fred! On Tue, 26 Sep 2017 14:08:56 -0700 (PDT) Fred Wright via devel wrote: > Resending with the correct subject. > > On Tue, 26 Sep 2017, Eric S. Raymond wrote: > > Fred Wright via devel : > > > > Plus these are most likely too late for 1.0. We are in the > > > > final testing phases now

Re: Python Library Cleanups

2017-09-26 Thread Fred Wright via devel
Resending with the correct subject. On Tue, 26 Sep 2017, Eric S. Raymond wrote: > Fred Wright via devel : > > > Plus these are most likely too late for 1.0. We are in the final > > > testing phases now. > > > > I think requiring users to set PYTHONPATH to run the tools should be > > considered a

Re: Python Library Cleanups

2017-09-26 Thread Gary E. Miller via devel
Yo Fred! On Tue, 26 Sep 2017 00:15:04 -0700 (PDT) Fred Wright via devel wrote: > If the directory choice on gentoo is inappropriate, take that up with > whomever packaged Python for it. Not Gentoo, the FHS. And the package I am using is git head. RGDS GARY

Re: Python Library Cleanups

2017-09-26 Thread Gary E. Miller via devel
Yo Daniele! On Mon, 25 Sep 2017 22:24:39 -0600 Daniele Nicolodi via devel wrote: > > The default gentoo PYTHONPATH onlly looks for system installed > > python libs. We don't want to install NTPsec python files in the > > system reserved directories. Thus PYTHONPATH is the only > > solution.

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Hal Murray : > > And I would so regard it if [setting PYTHONPATH] were ever required on > > Linux or FreeBSD. I have had no report of this. > > It's required on Fedora. I set it up ages ago. I think that was the > > I get the same on FreeBSD. Well, shit. That changes things. Now we have to

Re: Python Library Cleanups

2017-09-26 Thread Hal Murray via devel
> I will audit them, but dropping this in the day before release doesn't just > seem like asking for trouble, it seems like screaming WE WANT TO EMBARRASS > OURSELVES. Then put it on the known glitch list and fix it in 1.x > And I would so regard it if this were ever required on Linux or FreeB

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Fred Wright via devel : > > Plus these are most likely too late for 1.0. We are in the final > > testing phases now. > > I think requiring users to set PYTHONPATH to run the tools should be > considered a show stopper for a 1.0 release. And I would so regard it if this were ever required on Linu

Re: Python Library Cleanups

2017-09-26 Thread Eric S. Raymond via devel
Daniele Nicolodi via devel : > Delivering a 1.0 release that requires fiddling with PYTHONPATH to use > the application would make the project look like it is run by amateurs. > I think that is not the impression you want to give. I'm sensitive to this issue. PYTHONPATH fiddling is never required

Re: Python Library Cleanups

2017-09-26 Thread Fred Wright via devel
On Mon, 25 Sep 2017, Gary E. Miller via devel wrote: > On Mon, 25 Sep 2017 20:26:44 -0700 (PDT) > Fred Wright via devel wrote: > > > 1) Waf misuses get_python_lib() in a way that often gets the wrong > > result, with the effect of installing the libraries in a location > > where Python doesn't lo

Re: Python Library Cleanups

2017-09-25 Thread Daniele Nicolodi via devel
On 25/09/17 21:56, Gary E. Miller via devel wrote: > On Mon, 25 Sep 2017 20:26:44 -0700 (PDT) > Fred Wright via devel wrote: > >> 1) Waf misuses get_python_lib() in a way that often gets the wrong >> result, with the effect of installing the libraries in a location >> where Python doesn't look fo

Re: Python Library Cleanups

2017-09-25 Thread Gary E. Miller via devel
Yo Fred! On Mon, 25 Sep 2017 20:26:44 -0700 (PDT) Fred Wright via devel wrote: > 1) Waf misuses get_python_lib() in a way that often gets the wrong > result, with the effect of installing the libraries in a location > where Python doesn't look for them. This led to various > inappropriate recom

Python Library Cleanups

2017-09-25 Thread Fred Wright via devel
I finally have the fixes I've been working on related to the Python library setup ready for publication. The important issues were: 1) Waf misuses get_python_lib() in a way that often gets the wrong result, with the effect of installing the libraries in a location where Python doesn't look for t