On 27/01/2010 11:21, David Lyon wrote:
Glen wrote:
So let's further say that the .zip file was named .py, instead, but was
a .zip internally.

So this cures the icon too, maybe you realized that.
It takes it to 80% cured.

Being the purist that I am I still long for the day when I
can see a python package in my file manager with a proper
icon. Icons only cost $400 to get done professionally at
a graphic artist. That's roughly the same as a round of
drinks at a python conference.
If you install Python packages from

I'd like to see a pythonic egg icon. I know from experience
graphic artists can knock together a nice set pretty easily.

A ZIP named .py doesn't need to be "installed" it can just run in
place.  And as a couple other subthreads noted, this is already
functional in Python 2.6/3.1 today.
It's not that I forget or didn't understand, it's that the inplace
concept doesn't sit nicely in a formal windows environment. You have
to accept my word that there is a 'tradition', started by Microsofts
'guidelines' over 20 years ago about where windows users must put their
programs.

But a module or a package isn't a program. If a Python programmer wants to create an application that is properly 'installed' on Windows then the *right* thing to do is to create an installer - and that uses infrastructure not provided by a language, but that is built into Windows. Tools like Wix are used to build Windows installers, Python does not need to do anything specific to support this. Java, C#, C++ and none of the other major programming languages support this *in the language* because it isn't the right place to do this.

I can tell you about places where I have contracted where the
desktops are "cleaned" of any "inplace" files. If I spent a
week doing an application, I would want it to last on a system
well into the next day..

To get around that, we simply put the programs where microsoft
tell us and the data similarly and everything is sweet.

If the programmer is building applications for Windows then they should create an installer that installs into the right place. No argument about that. Python doesn't need to, and *shouldn't* do anything to accommodate that.

All the best,

Michael Foord

--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of 
your employer, to release me from all obligations and waivers arising from any 
and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, 
clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and 
acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your 
employer, its partners, licensors, agents and assigns, in perpetuity, without 
prejudice to my ongoing rights and privileges. You further represent that you 
have the authority to release me from any BOGUS AGREEMENTS on behalf of your 
employer.


_______________________________________________
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

Reply via email to