On Thu, Jun 10, 2004 at 06:56:53PM -0400, Tim Peters wrote:

[Mark W. Alexander] ...

...

If it's a "Fred thing", then call me Fred ;) I despise having to call whatever.sh, something.py and heavenforbid.pl. From the command line, what do I care what the script is written in, or even if it's a script, an ELF. or an alias. Extensions are fine for developers, because they need to know implementation details. User's do not, and making them know is just rude (IMNSHO).

You can't tell me about users: I have two sisters <wink>. For years, they saw ".pdf" and ".html" etc as just part of the file name. "." didn't mean anything special to them -- that's a learned convention. Then again, my definition of "user" doesn't include people who run scripts from shell windows either.

Sisters?! Wait 'til you have a wife & kids! I think we're agreed that extensions stay on Windows scripts. On *nix, I think they're a nuisance on executables. Also note that official Debian packages strips the .pl, .py, .sh, etc., extensions off when upstream developers don't, I _think_ as a matter of policy. So maybe we're back to a bdist_* based implementation? mwa -- Mark W. Alexander slash@dotnetslash.net The contents of this message authored by Mark W. Alexander are released under the Creative Commons Attribution-NonCommercial license. Copyright of quoted materials are retained by the original author(s). http://creativecommons.org/licenses/by-nc/1.0/