I'm new to python programming, and want to try to edit scripts in IDLE instead of the OSX command line. However, when I try to start it, it gives me the error "Idle Subprocess didn't make a connection. Either Idle can't start a subprocess or personal firewall software is blocking the connection." I don't have a firewall configured, so what could the problem be?
A:
You can try running IDLE with the "-n" option. From the IDLE help:
Running without a subprocess:
If IDLE is started with the -n command line switch it will run in a single process and will not create the subprocess which runs the RPC Python execution server. This can be useful if Python cannot create the subprocess or the RPC socket interface on your platform. However, in this mode user code is not isolated from IDLE itself. Also, the environment is not restarted when Run/Run Module (F5) is selected. If your code has been modified, you must reload() the affected modules and re-import any specific items (e.g. from foo import baz) if the changes are to take effect. For these reasons, it is preferable to run IDLE with the default subprocess if at all possible.
ars
2010-07-19 01:40:03
A:
You don't say which version of Python or OS X you are using but, if you are trying to use the IDLE installed by the recent python.org 64-bit installer for Python 2.7, you are almost certainly running into a known issue. As noted in the bug report, until the problem with the 2.7 installer is resolved, the simplest workaround for 2.7 is to install the 32-bit-only version of 2.7 using the 10.3 and up
installer.
Ned Deily
2010-07-19 04:36:45
I am using 2.7 on Mac OSX 10.6.4. I'm pretty sure it's the 64 bit version. Is there a huge difference between me using the 64 bit process and me using the 32 bit process? How do I downgrade?
Ian
2010-07-19 14:47:50
Crudely put, the difference between 32-bit and 64-bit Python is largely one of better performance when dealing with certain types of problems, for example ones involving very large sets of data or very large integers. Most likely you won't notice any difference. To downgrade, just load the other installer from python.org and install it just like you installed the first time. It will overwrite the original files installed. If you have installed any additional Python packages already (typically something using a setup.py script), you will need to reinstall them afterwards.
Ned Deily
2010-07-19 18:56:04