Groups > linux.debian.maint.python > #8212

Re: Python Policy: Things to consider for Stretch

From	Barry Warsaw <barry@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Python Policy: Things to consider for Stretch
Date	2016-02-16 02:20 +0100
Message-ID	<r2Ct4-Dq-11@gated-at.bofh.it> (permalink)
References	<qTpEL-7eF-19@gated-at.bofh.it> <qTSQp-28S-1@gated-at.bofh.it> <r2Bnj-8m8-3@gated-at.bofh.it> <r2C01-aC-7@gated-at.bofh.it> <r2C9J-dV-15@gated-at.bofh.it>
Organization	The Organization of Unorganized Woozalists

Show all headers | View raw

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 && make
install' always put Python in /usr/local by default.  I think it was pretty
much the defacto standard for non-vendor supplied software[*] back in the days
of IRIX, SunOS, and other early *nix OSes that Python was developed on.  So it
was therefore completely natural that you'd end up with a site-packages in
/usr/local.  It was only later that the /usr/local site-packages directory
ended up on a /usr pathed distro-provided Python, which of course led to the
previously discussed dist-packages, the location of which completely mirrors
site-packages.

>I find it weird that site- gets used in ~/ since they are clearly user
>packages not site/system-wide packages.

It's all just a big ball of cruft-on-cruft with backward compatibility
preventing most cullings.  Somewhere out there, the entire world financial
system probably still critically depends on a tiny bit of Python 1.3 that
nobody has anything but the .pyc files for any more. ;)

Cheers,
-Barry

[*] I can't even call it Free Software or Open Source because it predates
those terms.  I mean, I started out sharing split shar files on Usenet with my
UUCP address.  ObGOML.

Thread

Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-21 16:50 +0100
  Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-01-23 00:00 +0100
    Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-23 09:40 +0100
      Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-01-24 03:00 +0100
        Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 04:10 +0100
          Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-24 06:40 +0100
            Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 07:10 +0100
            Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-01-24 19:10 +0100
            Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-26 07:00 +0100
            Re: Python Policy: Things to consider for Stretch Dmitry Shachnev <mitya57@debian.org> - 2016-01-26 18:00 +0100
              Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-27 04:40 +0100
                Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-27 05:20 +0100
                Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-27 10:50 +0100
            Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-29 23:30 +0100
              Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-30 00:10 +0100
    Re: Python Policy: Things to consider for Stretch Paul Wise <pabs@debian.org> - 2016-02-16 01:10 +0100
      Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-02-16 01:50 +0100
        Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-02-16 02:00 +0100
        Re: Python Policy: Things to consider for Stretch Paul Wise <pabs@debian.org> - 2016-02-16 02:00 +0100
          Re: Python Policy: Things to consider for Stretch Barry Warsaw <barry@debian.org> - 2016-02-16 02:20 +0100
  Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-24 06:50 +0100
    Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-24 07:00 +0100
      Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 07:20 +0100
        Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-01-25 06:00 +0100
          Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-25 06:30 +0100
    Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-01-24 07:10 +0100
  Re: Python Policy: Things to consider for Stretch Scott Kitterman <debian@kitterman.com> - 2016-02-15 23:30 +0100
    Re: Python Policy: Things to consider for Stretch Ben Finney <ben+debian@benfinney.id.au> - 2016-02-16 03:50 +0100

csiph-web