Yo Fred!
On Thu, 28 Sep 2017 19:25:06 -0700 (PDT)
Fred Wright via devel wrote:
> Interestingly enough, this last paragraph is both completely
> irrelevant to the issue at hand, and simultaneously gets to the crux
> of the matter. :-)
Always my intention .
> The whole issue being discussed here
On Tue, 26 Sep 2017, Gary E. Miller via devel wrote (different thread):
> On Tue, 26 Sep 2017 22:04:53 -0400 (EDT)
> "Eric S. Raymond via devel" wrote:
>
> > 2. Keep Fred's patch. Ship 1.0 with FHS non-conformance as a known
> >and documented bug.
>
> Gack. Opening a tech support nightmare.
Yo Hal!
On Wed, 27 Sep 2017 23:50:51 -0700
Hal Murray via devel wrote:
> Is the install location fixed at configure time, or can that be
> specified at install time?
None of the above. Packagers do it after the install to a temp
location.
RGDS
GARY
Yo Hal!
On Wed, 27 Sep 2017 23:35:23 -0700
Hal Murray wrote:
> > Once again, I think pip has the answer: edit the sys.path.
>
> Why is editing sys.path better than using PYTHONPATH?
Editing the config file that stores sys.path is persistent, and used
by all python that uses that path.
PYTH
Yo Fred!
On Wed, 27 Sep 2017 19:02:23 -0700 (PDT)
Fred Wright via devel wrote:
> First of all, in order for an import to work in Python, the directory
> containing the module needs to be in sys.path at the time of the
> import. This requirement can be met in one of two ways:
Yup.
> One of the
My inclination is to keep his patch, document the lack of FHS compliance,
and roadmap a fix to get_python_lib, possibly by nudging the WAF or python
communities to write it.
And we again specifically thank Fred for his patch.
..m
On Wed, Sep 27, 2017 at 4:39 AM Eric S. Raymond via devel
wrote:
