[Pyobjc-dev] [ pyobjc-Bugs-1844495 ] Cannot clean up PyObjC to get back memory with Py_Finalize

[SourceForge.net <no...@so...>]

Bugs item #1844495, was opened at 2007-12-04 16:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=1844495&group_id=14534

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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andy Kim (andypotion)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot clean up PyObjC to get back memory with Py_Finalize

Initial Comment:
Summary:

When embedding Python into a Cocoa application, you can't call Py_Finalize() to reclaim memory because if you call Py_Initialize() again to start another interpreter, it can't import the objc module the second time.


Steps to Reproduce:

1. Build and launch the included test application.
2. Click the "Run With Foundation" button once. It will execute a very simple python file and clean up.
3. Click the "Run With Foundation" button again. You will see problems in the console this time.

When you click the "Run Without Foundation" button multiple times, there are no problems.


Test System:

MacBook Pro Intel Core 2 Duo running Mac OS X 10.5.1


Notes:

It seems that once you load the PyObjC bridge, you cannot unload it. Is this intended behavior?

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=1844495&group_id=14534