[Pythonmac-SIG] StandAlone Python Application Does not Release Python

Bob Swerdlow rswerdlow at transpose.com
Fri Aug 20 23:24:41 CEST 2004


I'm building a stand-alone Python application using PyObjC 1.1 and Python
2.3 on Panther.  We've run into a problem: when we make a new release, the
users find that they cannot copy it over the old release, even after they
have quit the application - the Finder reports "The operation cannot be
completed because the item 'Python' is in use."

This only happens if the old release has been run and then quit.  I look in
the Activity Monitor and I don't see any processes from our application
still running and the rest of my processes don't have that file open. The
file that is "still in use" is
MyApp.app/Contents/Frameworks/Python.framework/Versions/2.3/Python (I know
because if I rename that file, the warning message reports the new name).

If the user manually moves the old application to the trash then the new
version can be copied with a problem.  However, why is that file still in
use and how do I avoid this?

Thanks for your help,
Bob




More information about the Pythonmac-SIG mailing list