The Python 2.3.3 windows installer sets a file 
association for .py files - 'edit with IDLE'.

It sets this up to launch IDLE with the command line '-n' 
which is *without* a subprocess.

I set up a new file association to launch IDLE with 
subprocess enabled. If IDLE ever attempts to open a 
second shell window with subprocess it hangs and I 
have to kill the process.

Is this a known limitation or a bug (?)  - if the latter 
why does the installer default to using the -n flag. 

I asked on comp.lang.python and surprisingly got no 
answer - perhaps the time of year has something to do 
with it. :-)

My prefferred email address for contact is fuzzyman AT 
atlantibots DOT org DOT uk

Logged In: YES 
user_id=149084

This is a known limitation.  Currently only one subprocess may
exist because only one port is used.  I plan to expand this in
the future. 

Recommend you stay with the default binding.

This duplicates IDLEfork Patch 661363.  Closing as dup.