[ python-Bugs-1568075 ] GUI scripts always return to an interpreter

SourceForge.net noreply at sourceforge.net
Sat Sep 30 23:48:24 CEST 2006


Bugs item #1568075, was opened at 2006-09-29 16:00
Message generated for change (Comment added) made by jejackson
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1568075&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: Open
Resolution: None
Priority: 5
Submitted By: jjackson (jejackson)
Assigned to: Jack Jansen (jackjansen)
Summary: GUI scripts always return to an interpreter

Initial Comment:
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.


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

>Comment By: jjackson (jejackson)
Date: 2006-09-30 14:48

Message:
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.

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

Comment By: Georg Brandl (gbrandl)
Date: 2006-09-30 11:24

Message:
Logged In: YES 
user_id=849994

Could you check if it is set? (using
echo $PYTHONINSPECT in a console?)

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

Comment By: jjackson (jejackson)
Date: 2006-09-30 10:55

Message:
Logged In: YES 
user_id=1497873

No, I didn't set the PYTHONINSPECT env variable. If it was set, it was by 
something else.

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

Comment By: Georg Brandl (gbrandl)
Date: 2006-09-30 00:47

Message:
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.

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

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


More information about the Python-bugs-list mailing list