
On 21-jun-04, at 18:54, Fred L. Drake, Jr. wrote:
On Tuesday 15 June 2004 01:07 am, Ronald Oussoren wrote:
Please don't, unless MacOS X is treated differently than other unices. There is a minor difference between GUI and non-GUI scripts on OSX (due to a misfeature of the OS).
--sigh--
So as I understand it, you'd need an extension to be left on for .pyw scripts, but could tolerate removal of extensions for other scripts. This is a distinct case from other Unixes and from Windows.
I really have to start reading my own mails some time... What I tried to say is "please don't ignore scripts with a .pyw extension in the scripts argument of setup". With MacOS X it all depends on how you look at things :-). If you want to start scripts by double-clicking on them they should have an extension (either .py or .pyw), if you're a unix-head that starts scripts from the shell the extension is annoying. IMHO the only correct way for installing GUI programs on MacOS X is creating an application bundle (which is a directory with a special structure). But that's just one opinion, and not necessarily relevant for this discussion. Ronald -- X|support bv http://www.xsupport.nl/ T: +31 610271479 F: +31 204416173