[ python-Bugs-1527397 ] PythonLauncher uses incorrect working directory

[SourceForge.net]

Bugs item #1527397, was opened at 2006-07-23 10:29
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1527397&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Macintosh
Group: Python 2.5
>Status: Closed
Resolution: Fixed
Priority: 7
Submitted By: Bob Ippolito (etrepum)
Assigned to: Ronald Oussoren (ronaldoussoren)
Summary: PythonLauncher uses incorrect working directory

Initial Comment:
PythonLauncher, the application used to launch .py files by double-click, 
does not launch with the correct working directory. This means that any 
script that depends on data files will not work via PythonLauncher.

Users expect the working directory to be that of the launched script, like 
on other platforms, but PythonLauncher launches with a working directory 
of $HOME.

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2006-08-15 19:20

Message:
Logged In: YES 
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Ronald Oussoren (ronaldoussoren)
Date: 2006-08-01 14:02

Message:
Logged In: YES 
user_id=580910

Fixed in revision 51028. Please confirm.

The same revision also fixes a problem where PythonLauncher failed to launch 
scripts if the name contains quotes (e.g. "Ronald's Script.py").

----------------------------------------------------------------------

Comment By: Ronald Oussoren (ronaldoussoren)
Date: 2006-07-23 11:50

Message:
Logged In: YES 
user_id=580910

I agree that the current behaviour is not what users expect and should be 
considered a bug.

I'd like to get the attached patch into 2.5, it changes the CWD to the directory 
containing the script and should be perfectly save.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1527397&group_id=5470