changeset: 98228:b5c8a40d4240 branch: 2.7 parent: 98224:5a60fdd9af8c user: Terry Jan Reedy date: Wed Sep 23 20:02:25 2015 -0400 files: Lib/idlelib/help.html description: Issue 25224: Augment Idle doc feature list and no-subprocess section to finish making current README.txt obsolete. diff -r 5a60fdd9af8c -r b5c8a40d4240 Lib/idlelib/help.html --- a/Lib/idlelib/help.html Wed Sep 23 20:00:22 2015 -0400 +++ b/Lib/idlelib/help.html Wed Sep 23 20:02:25 2015 -0400 @@ -80,10 +80,15 @@

24.6.4.2. Running without a subprocess

+

By default, Idle executes user code in a separate subprocess via a socket, +which uses the internal loopback interface. This connection is not +externally visible and no data is sent to or received from the Internet. +If firewall software complains anyway, you can ignore it.

+

If the attempt to make the socket connection fails, Idle will notify you. +Such failures are sometimes transient, but if persistent, the problem +may be either a firewall blocking the connecton or misconfiguration of +a particular system. Until the problem is fixed, one can run Idle with +the -n command line switch.

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