[Python-ideas] About PEP-582

Philip Bergen pbergen at salesforce.com
Tue Feb 19 18:28:14 EST 2019


First attempt at this, so please be gentle. :)
I am very interested in the overall goal of not needing virtualenvs, but
I'm curious about the motivations behind pep-582.
Could someone help me understand if this has previously been discussed and
in that case why it was decided against?
1: Why only look in CWD and not traverse root-wise?
2: It feels to me like there is a larger story here about sprucing up
PYTHONPATH.

About 2) I would prefer if we had a mechanism to automatically look for
.pythonpath.pth (or something with a better name, but to that effect). Then
we were not limited to a specific directory or location. This would
streamline cross project repos, for instance: you could have docker images
that came preloaded with common libraries and just add a layer with your
specifics in a different directory earlier in the paths specified by
.pythonpath.pth

Using pip to install into your directories of choice is already supported,
although perhaps we should have some way of telling it to use the first
entry in .pythonpath.pth.

I would be very grateful for some interaction on this. If there is general
interest I could submit some working code.

Thanks,
// Phil

-- 
*Philip Bergen*
P: +1(415)200-7340
*"Without data you are just another person with an opinion" -- W. Edwards
Deming*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20190219/36411d15/attachment-0001.html>


More information about the Python-ideas mailing list