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

Bob Ippolito bob at redivi.com
Fri Aug 20 23:44:05 CEST 2004


On Aug 20, 2004, at 5:24 PM, Bob Swerdlow wrote:

> 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?

I think this has something to do with the fact that bundlebuilder uses 
a script stub that is execve'd.  You should try using the PyObjC Xcode 
template until there is a release of py2app or bundlebuilder2 that uses 
a proper executable stub.

-bob



More information about the Pythonmac-SIG mailing list