From 328e1ecbce6745ba7aa3ad974ff34ef820f693cc Mon Sep 17 00:00:00 2001 From: Terry Jan Reedy Date: Wed, 23 Sep 2015 20:02:25 -0400 Subject: Issue 25224: Augment Idle doc feature list and no-subprocess section to finish making current README.txt obsolete. --- Lib/idlelib/help.html | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/Lib/idlelib/help.html b/Lib/idlelib/help.html index be4f52a..b2948a3 100644 --- a/Lib/idlelib/help.html +++ b/Lib/idlelib/help.html @@ -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 -- cgit v0.12