[Python-Dev] First draft of "sysconfig"

David Lyon david.lyon at preisshare.net
Thu Dec 17 03:10:48 CET 2009

On Wed, 16 Dec 2009 21:21:01 +1000, Nick Coghlan <ncoghlan at gmail.com>

> .. we mostly leave that to the py2exe/py2app + native installer
> developers of the world. There are a *lot* of thorny issues in getting
> installers fully in accordance with OS developer guidelines, which is
> why we tend to shy away from it.

And that is fair enough. In the commercial world, once the python
gets compiled, you're mostly talking about some application where
the source code needs protection. The bar is raised - to match
the available budgets.

However, I would like to point out a category of applications
that live in source code form. Inside scientific or commercial
organisations. These are apps that are never compiled - and 
just run in interpreted mode. Maybe they're on workstations,
or maybe they're on web servers. It doesn't matter that much.

The point is that the python Configurations exist over many 

What I'd like to suggest is that python apps are becoming more
network centric. To the point where it might at some time in the
future it might well become a 'python-core' issue.

I'm not suggesting writing a new SCM because so many already
exist. And in python too - haha - how great is that.

All that I'm doing is suggesting that the python of the future
and the stdlib of the future will include celery or superpy
or the mercurial or bzr interfaces, and it will be really
easy to roll out the 'helloworld.py' app/web-app out to 
the desktop machines or django server or cluster or cloud 
of machines wherever they actually are. 

The machines will just have 'python' installed, and then from 
there everything will pretty easily take place (apps/packages
get pushed to remote machines). 

I'm not star-gazing, because all these things are already
needed and already being done to some degree in some
organisations. There's already the libraries on pypi for
most of this anyway.

The practical advantages of some of us going in this direction 
is that it might be possible for us open sourcers to attract
the attention of our commercial sponsors attention. Because
they're always interested in getting new toys and utilising
their resources in the most efficient way. 

If we do the above, incorporate tested packages from pypi, it's
possible that the glow of CPAN might be tarnished somewhat.


More information about the Python-Dev mailing list