[Pythonmac-SIG] cwd and PythonLauncher problem
Jim Harrison
jhrsn at pitt.edu
Thu Sep 30 14:47:01 CEST 2004
Sorry if this has been previously discussed. It appears that when a source
file is double-clicked and starts with PythonLauncher (2.3), the directory
of the file is not added to the Python module search paths. Thus other
modules in that directory cannot be imported without a full path and files
cannot be read or written using paths relative to the source file.
IDLE, the Mac PythonIDE and the Windows implementation of Python seem to
handle this correctly. The original launcher with MacPython (in the distant
past) also handled this (PyOXIDE, on the other hand, seems to show the
problem). Is a fix for this available or under consideration (with respect
to the Launcher)? Or is this something that I've screwed up?
Jim Harrison
Univ. of Pittsburgh
More information about the Pythonmac-SIG
mailing list