Fix for Python library path problem

Eric S. Raymond esr at thyrsus.com
Thu Sep 28 03:49:38 UTC 2017


Jason Azze <jason.azze at gmail.com>:
> On Sep 27, 2017 8:51 PM, "Eric S. Raymond via devel" <devel at ntpsec.org>
> wrote:
> 
> Gary E. Miller via devel <devel at ntpsec.org>:
> > > I thought you just told me the opposite,
> >
> > Sorry if I was not clear the first time.
> >
> > > and I *know* Jason did.
> >
> > I sugggest you reconfirm with him.
> >
> > Re-reading the emails I see a bunch of double negatives going around.
> 
> Great.  Now I don't think I know *anything.*
> 
> 
> ESR provided two test lines. The first returned some path stuff for me. The
> second returned an empty pair of square brackets.
> 
> My reading of ESR's call for testing was that that was the hoped for result
> and that if the second expression had returned anything, that would have
> been bad.

That is correct.   Those lines were intended to test this rule:

"If /usr/lib/X/Y is in sys.path, then /usr/local/lib/X/Y is in sys.path"

Jason's test confirmed the rule.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.




More information about the devel mailing list