On 23 Aug, 2013, at 3:44, Terry Reedy <[email protected]> wrote: > On 8/21/2013 10:02 PM, Terry Reedy wrote: >> On 8/4/2013 5:07 PM, Arie Schlesinger wrote: >>> Hello, >>> I try to work with python 3.3.2 on macbook-air 10.8, but IDLE won't >>> open. >>> It writes "IDLE's subprocess didnit make connection.." > > You might try to run > python -m test test_socket test_subprocess > and report the result.
Why? Running IDLE from the command-line is IMHO more interesting, both with: $ idle3.3 # located in /Library/Framework/Python.framework/Versions/3.3/bin and $ "/Applications/Python 3.3/IDLE.app/Contents/MacOS/IDLE" The first command starts IDLE the same way as on other platforms, the latter is the command used to start IDLE from the OSX GUI. Another command to try: $ python3.3 -c 'import idlelib.run; idlelib.run.main()' 900 That is basicly how IDLE starts its subprocess (900 is a random port number). This should print that IDLE cannot cannot connect to the main proces, on my machine followed by a hard hang that requires a force quit because the child process tries to use Tk from a thread that isn't the main thread: IDLE Subprocess: socket error: Connection refused, retrying.... IDLE Subprocess: socket error: Connection refused, retrying.... IDLE Subprocess: socket error: Connection refused, retrying.... IDLE Subprocess: Connection to IDLE GUI failed, exiting. 2013-08-23 07:49:04.670 Python[3793:1803] NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on void _NSAlertWarnUnsafeBackgroundThreadUsage() to debug. This will be logged only once. This may break in the future. (The last line is acompanied by a small white empty window) Ronald > > > -- > Terry Jan Reedy > > _______________________________________________ > IDLE-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/idle-dev _______________________________________________ IDLE-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/idle-dev
