Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Scott Kitterman
On Tuesday, February 02, 2016 06:44:57 AM Ben Finney wrote: > Ben Finney writes: > > * Address all the language around Python 2 versus Python 3 versus > > > > Python general, and re-order or re-word to focus *primarily* on Python > > 3, with Python 2 treated as the still-supported legacy syst

Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Paul Wise
On Sat, Jan 23, 2016 at 9:55 AM, Barry Warsaw wrote: > 2.5 Module Path > > "Public Python modules must be installed in the system Python modules > directory, /usr/lib/python./dist-packages. Public Python 3 modules must > be installed in /usr/lib/python3/dist-packages." Side-note: does anyone kno

Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Barry Warsaw
On Feb 16, 2016, at 11:05 AM, Paul Wise wrote: >Side-note: does anyone know why Python puts packages in "dist-packages", >"site-packages" etc directories instead of just "packages" directories? I don't remember exactly why we called it 'site-packages', but I believe it was an evolution from the e

Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Barry Warsaw
On Feb 15, 2016, at 07:42 PM, Barry Warsaw wrote: >I don't remember exactly why we called it 'site-packages', but I believe it >was an evolution from the earlier ni.py module, which was where dotted module >paths first showed up in Python. And which had a 'site-python' directory, which was kept a

Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Paul Wise
On Tue, Feb 16, 2016 at 11:42 AM, Barry Warsaw wrote: > I don't remember exactly why we called it 'site-packages' ... Thanks for the history :) I always thought it strange to put site- in /usr/local since /usr/local already implies site/system-wide packages. Same for dist- since /usr already imp

Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Barry Warsaw
On Feb 16, 2016, at 11:54 AM, Paul Wise wrote: >I always thought it strange to put site- in /usr/local since >/usr/local already implies site/system-wide packages. Same for dist- >since /usr already implies distribution packages. For as long as I can remember, a from-source 'configure && make &&

Re: Python Policy: Things to consider for Stretch

2016-02-15 Thread Ben Finney
Scott Kitterman writes: > On Tuesday, February 02, 2016 06:44:57 AM Ben Finney wrote: > > Ben Finney writes: > > > * Address all the language around Python 2 versus Python 3 versus > > > Python general, and re-order or re-word to focus *primarily* on > > > Python 3, with Python 2 treated as the