Bugs item #1568075, was opened at 2006-09-29 16:00 Message generated for change (Tracker Item Submitted) made by Item Submitter 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1568075&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
