This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: GUI scripts always return to an interpreter
Type: Stage:
Components: macOS Versions: Python 2.5
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: jackjansen Nosy List: georg.brandl, jackjansen, jejackson
Priority: normal Keywords:

Created on 2006-09-29 23:00 by jejackson, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (6)
msg30066 - (view) Author: jjackson (jejackson) Date: 2006-09-29 23:00
I installed the latest version of 2.5 from the web last night:

Python 2.5 (r25:51918, Sep 19 2006, 08:49:13) 
[GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin

When I run a wxPython script, using something like

pythonw myScript.py

from the Terminal, I find myself in an interpreter after I use the quit 
menu. The menubar becomes a single, hung python menu, and a shell 
window pops up with an interpreter prompt. Cntrl-D kills the interpreter.

It's as if python was stuck in "-i" mode:

pythonw -i myScript.py

gives the same results.

(python and pythonw give the same results. It appears from comments on 
the web that they are now the same. They appear so from a diff. If so, why 
not a symlink?)

Running the lastest wxPython demo gives this warning in the console, 

2006-09-29 15:40:06.681 wxPython Demo[942] WARNING: 
_wrapRunLoopWithAutoreleasePoolHandler got kCFRunLoopExit, but there 
are no autorelease pools in the stack.

which may or may not be related.
msg30067 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2006-09-30 07:47
Logged In: YES 
user_id=849994

Did you (or someone else) perhaps set the PYTHONINSPECT
environment variable? I can't imagine another cause for this
problem.
msg30068 - (view) Author: jjackson (jejackson) Date: 2006-09-30 17:55
Logged In: YES 
user_id=1497873

No, I didn't set the PYTHONINSPECT env variable. If it was set, it was by 
something else.
msg30069 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2006-09-30 18:24
Logged In: YES 
user_id=849994

Could you check if it is set? (using
echo $PYTHONINSPECT in a console?)
msg30070 - (view) Author: jjackson (jejackson) Date: 2006-09-30 21:48
Logged In: YES 
user_id=1497873

I tried:

Olivos:~ jj$ echo $PYTHONINSPECT

Olivos:~ jj$ 

Looks like it isn't set. 

However, this might be a wxPython bug. I tried a tcl/tk app from the demos:
Applications/MacPython 2.5/Extras/Demo/tkinter/guido/solitaire.py.

Quitting it worked fine. 

I'll post something on the wxPython mac list.
msg30071 - (view) Author: jjackson (jejackson) Date: 2007-01-30 21:20
After a bunch of troubleshooting, I've determined that the problem is caused by the Unsanity Application Enhancer Module (APE) 2.0.2. Deactivating or removing that module and the problem goes away. Maybe they are patching something that causes the python.app to hang on exit.

I've set the resolution to invalid as this is not wxpython or python's problem.
History
Date User Action Args
2022-04-11 14:56:20adminsetgithub: 44056
2006-09-29 23:00:03jejacksoncreate