🌐 Mailman 3 February 2003 - Pythonmac-SIG - python.org

more on PythonLauncher
by Kevin Altis Feb. 3, 2003

Feb. 3, 2003

Another reason for PythonLauncher to simply default to using pythonw, is that PythonLauncher has no purpose except in the context of the Finder, right? Do tkinter scripts require pythonw? How about PyObjC? In other words, do we have Python scripts that it makes sense to run from the Finder that aren't GUI scripts that require pythonw? Is PythonLauncher ever relevant to command-line scripts or CGI scripts? Would the user run scripts that use something like curses or readline for interactive input from the Finder; wouldn't they just use the Terminal? And again, if pythonw was used to run those types of scripts, what would the downside be? ka

2 1

fixing the PATH environment variable for 2.3
by Kevin Altis Feb. 3, 2003

Feb. 3, 2003

To simplify using the "right" Python (aka 2.3a1 not Apple's 2.2), I added /usr/local/bin back to the PATH environment variable, by adding PATH to my ~/.MacOSX/environment.plist file. <key>PATH</key> <string>/usr/local/bin:/bin:/sbin:/usr/bin:/usr/sbin</string> If you like having your home directory as part of the PATH, you could use: <key>PATH</key> <string>/usr/local/bin:/bin:/sbin:/usr/bin:/usr/sbin:/Users/username</string > substitute your own username for "username" in the string above. See the following link for setting up your ~/.MacOSX/environment.plist file if you haven't already got one. http://www.astro.washington.edu/owen/AquaEnvVar.html I also created a simple .cshrc, since environment.plist doesn't seem to be getting picked up in the Terminal. The ~/.cshrc file just contains: setenv PATH /usr/local/bin:$PATH If you are using the bash shell you should create something similar for your .bashrc. Now you can just type python or pythonw in the Terminal and get the "right" Python. Scripts launched with PythonLauncher will also have the right PATH environment variable because of the environment.plist setting. I'm tempted to have a script that can automatically create these files for users if they don't already have them; those that have them should know enough to munge them if needed. Creating these files as a default part of the MachoPython install seems a bit much, but until Apple is distributing 2.3 (maybe this fall?), developers are probably going to want to modify their PATH. Other suggestions? ka

1 0

Fwd: [wxPython-mac] downside to just always using pythonw?
by Jack Jansen Feb. 2, 2003

Feb. 2, 2003

I'm forwarding this message that Kevin Altis sent to the wxPython mailing list earlier today, and I'd like to get feedback on it. On first thought I think I agree with it (the gist is: "make PythonLauncher always use pythonw, so the only difference between its treatment of .py and .pyw files is that the former get a console window"). There are some drawbacks (if you are developing a script that will eventually run in a windowless environment you will not notice it if your script calls to the window manager), but I think the advantage of more comprehensible behavior for novices outweighs that. Note that this would only mean that the default app for .py scripts would change, you'll always be able to change it back. Begin forwarded message: > From: "Kevin Altis" <altis(a)semi-retired.com> > Date: zon feb 2, 2003 00:00:53 Europe/Amsterdam > To: "Wxpython-Mac" <wxpython-mac(a)lists.wxwindows.org> > Subject: [wxPython-mac] downside to just always using pythonw? > Reply-To: wxPython-mac(a)lists.wxwindows.org > > I know that via the PythonLauncher we can automatically have scripts > with a > .pyw extension run with pythonw. However, most scripts brought over > from > Linux and Windows designed to run with wxPython are unlikely to have > the > .pyw extension set. Normally, the .pyw extension is only useful under > Windows when you want to suppress the console window being displayed > such as > when you run a script from the Explorer by double-clicking the file. > > So, either you train Mac OS X Python users to rename GUI scripts to > .pyw, > provide some utility to do the conversion, or setup PythonLauncher to > run > .py scripts by default with pythonw. The latter seems the simplest. > The vast > majority of the scripts I'll be running are GUI scripts and I also > need to > work on files out of cvs where it is not practical to rename the files > to > .pyw. I can always manually choose to use python instead of pythonw in > the > Terminal or hold down the Option/Alt key to bring up PythonLauncher if > I > specifically need to use /usr/local/bin/python. > > The question then becomes what are the downsides and likely errors that > would occur by just always using /usr/local/bin/pythonw instead of > /usr/local/bin/python? Is it simply a matter of using more memory and > slower > script startup because extra libs are loaded? I think we might want to > make > pythonw the default for even .py scripts if those are the only issues, > the > user can always change the Preference back to python. > > If someone could spell out the differences and/or suggest alternative > approaches to using pythonw and .pyw scripts that would be welcome. > Right > now I forsee endless messages on the mailing lists and c.l.py from > confused > users when scripts don't run or run, but don't work correctly because > parts > of the framework are unavailable. > > ka > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wxPython-mac-unsubscribe(a)lists.wxwindows.org > For additional commands, e-mail: wxPython-mac-help(a)lists.wxwindows.org > -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

2 1

error using python
by NetBrick62＠aol.com Feb. 1, 2003

Feb. 1, 2003

Whenever I try to open Python in X11 (or Terminal or XDarwin) I get the following error message: [Bricks-Computer:~] brick% python Python 2.2.1 (#1, 09/14/02, 00:14:43) [GCC Apple devkit-based CPP 6.02] on darwin Type "help", "copyright", "credits" or "license" for more information. dyld: python Undefined symbols: /sw/lib/libreadline.4.2.dylib undefined reference to _tgetent expected to be defined in /usr/lib/libSystem.B.dylib Trace/BPT trap [Bricks-Computer:~] brick% Could anyone over any suggestions, Im using the Carbon Python version now but would like to get back into Unix. Im running Mac OS X 10.2 Jaguar on a G3 Imac. Any help would be appreciated, Thank you for your time.

2 1