Re: [Python-Dev] First draft of "sysconfig"
David Lyon wrote: > I was thinking that perphaps sysconfig could help me get my > helloworld.py application into a \Program Files\hello world > directory and everything would be rosy. > > But not yet. So I will wait. No, 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. That said, we did add the zip archive execution capability so that complex Python applications can be more easily executed without needing to install them at all. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] First draft of "sysconfig"
On Wed, 16 Dec 2009 21:21:01 +1000, Nick Coghlan wrote: > .. 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 machines. 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. David ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] First draft of "sysconfig"
David Lyon writes: > 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. Sure. But in a volunteer project, it's beg, buy, or build. Begging has not worked, and it's not because people don't understand what you're saying. Nobody is saying that want you want is stupid or impossible, either. It's just that they have created those libraries you mention, they have built PyPI, they have written distutils and setuptools and others. *These work well enough* ... except for you, apparently. I have no problem with that, and you're welcome to beg. But IMO at this point you're coming close to crossing the line from begging to whining. There clearly is no interest in going down the road you propose. Post a bounty or build it yourself (you were pretty much done with something last time around, weren't you?), and either way use the usual channels (eg, PyPI) to distribute the product and accumulate user interest and support for future attempts at logrolling to get it into the stdlib. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] First draft of "sysconfig"
On Thu, 17 Dec 2009 12:18:00 +0900, "Stephen J. Turnbull" wrote: > > .. 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. > > ... > There clearly is no interest in going down the > road you propose. Hmm.. well.. projects like buildout, superpy and celery suggest that people are already working and thinking this way. Lots of companies use clusters of python computers and these needs will only increase over time. If it's only +1 from one person to make python more network centric with sysconfig in 2010, then so be it. Have a nice day. David ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
