This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients roger.serwy, terry.reedy
Date 2013-08-23.23:35:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Idle once used os.spawnv to open the user subprocess and 2.7 still does. Sockets were then used to interact with the subprocess. Since rev71746, 2011-8-3, 3.2+ use subprocess.Popen but still use sockets. A rare but continual problem is failure to make the socket connection.

In #16123, Amaury Forgeot d'Arc suggested "pipes?" The idea resurfaced again in current Idle-sig thread "Idle does not open on mac" (because socket connection timed out). Guido, who designed the current 2.x system, chimed in with "I would recommend trying to use the subprocess module."

A current python-list thread indicates that there can be problems with
"Running a command line program and reading the result as it runs"

In particular, "for line in p:" gets lines delayed (buffered) while
Peter Otten discovered that "for line in iter(p.stdout.readline, ''):" gets them as they are produced.

We first need to experiment running a simple echo server with python(w).exe.  I have not succeeded yet on Windows.
Date User Action Args
2013-08-23 23:35:04terry.reedysetrecipients: + terry.reedy, roger.serwy
2013-08-23 23:35:04terry.reedysetmessageid: <>
2013-08-23 23:35:04terry.reedylinkissue18823 messages
2013-08-23 23:35:03terry.reedycreate