[Python-Dev] First draft of "sysconfig"

Floris Bruynooghe floris.bruynooghe at gmail.com
Tue Dec 15 10:32:55 CET 2009

On Mon, Dec 14, 2009 at 11:39:02PM -0500, David Lyon wrote:
> On Tue, 15 Dec 2009 15:24:36 +1100, Mark Hammond
> <mhammond at skippinet.com.au>
> wrote:
> >>>> But under windows, an application developer might (as in probably
> >>>> would) like to install an application in \Program Files\someapp
> >>>> rather than hidden in the bowels of the python interpretor.
> > ...
> > I'm missing your point ....
> The point is that if somebody writes an application in C, they
> will generally speaking not want (under say linux) for that
> application to live in the C compiler directory.
> Same goes for many other languages.
> The point is not controversial in other languages. And it
> shouldn't be here either.

If I write a shared library under C I am expected to install it under
one of the default locations if I don't want to require people to have
to tweak things before they can use it.  I see no difference with
python modules or packages.  Any private modules or packages used by
an application built using python don't have to be on the sys.path by
default (in fact I would encourage them not to be).

> >> Distutils is stopping them.

Distutils isn't perfect but solves the need of installing public
modules and packages quite well.


Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org

More information about the Python-Dev mailing list