Chris, Thanks. Kevin's suggestion works fine and I prefer not to edit individual files.
I have noticed that changing the default app refuses to pick up the new PythonLauncher 0.1 for some reason, even if you tell it in 'Get Info' to change it for all .py and .pyw files. Weird. Rob On Mar 7, 2006, at 9:25 AM, Christopher Barker wrote: >> On Mar 7, 2006, at 8:10 AM, Kevin Ollivier wrote: > >>> I suspect what is happening is that Python Launcher is using the >>> system Python 2.3 installation instead of the Python 2.4 one you >>> installed. Do a Get Info on the demo.pyw file and see if it says >>> PythonLauncher (2.3.5) as the default app to open that file. If >>> it does, try changing it to PythonLauncher (PythonLauncher >>> version 0.1) and see if that helps. > > as I understand it, PythonLauncher respects the #! line of start up > scripts. That means that you could change the #! line in the > relevant scripts to something like: > > #!/usr/bin/env pythonw2.4 > > I like to put a version in my #! lines, as it document what version > I've tested with, and it lets me have scripts that use different > version on the same system. > > Will changing the default app for a given *.pyw script change it > for all *.pyw scripts? > > -Chris > > > > -- > Christopher Barker, Ph.D. > Oceanographer > > NOAA/OR&R/HAZMAT (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > [EMAIL PROTECTED] _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
