Python libs on Debian/Raspbian

Gary E. Miller gem at
Sat Dec 9 03:31:51 UTC 2017

Yo Hal!

On Fri, 08 Dec 2017 18:52:10 -0800
Hal Murray <hmurray at> wrote:

> devel at said:
> > We need to focus our default on helping the user that downloads our
> > source tar ball to install the build exactly where Python upstream
> > wants us to:   
> I don't care where it is installed.

Well, by default, you surely do.  You do not want a './waf install' to
overwrite any distro installed copy.

> I'm trying to make sure it works
> after it gets installed.

And it used to, broken starting from commit

> Do we have to use PYTHONPATH on Debian?

Ah, back on the merry-go-round.  The answer is well defined upstream
(distro and Python), but ONLY after wyou specify HOW you are installing.

Any .deb, from a debian repo, will install, in the distro specific
preferred location, and presumeably 'just work'.

Conversely, any plain '/waf install' by user/admin, from our source, 
should go in a place, that MUST require that location in to be in
PYTHONPATH.  This is a long standing Python convention, that got b roken
in commit 947e05e50613aff71abfb8bd4ffdf955d5882744

So, annoying as it can be, for the benefit of the casual ovserver to
this.  We need to stop mingling all these install cases that need to
be kept totally separate.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the devel mailing list