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 pitrou
Recipients ezio.melotti, ncoghlan, pitrou
Date 2010-08-04.22:50:45
SpamBayes Score 0.00021284059
Marked as misclassified No
Message-id <1280962247.74.0.724550733964.issue9517@psf.upfronthosting.co.za>
In-reply-to
Content
test.script_helper has a couple of dedicated functions to launch a Python interpreter instance in a subprocess. Unfortunately, it is little used and most test modules use their own ad hoc calls to subprocess instead.

Remedying the situation would require:
- adding functions to script_helper (currently, the available functions merge stdout and stderr together, which is clearly undesireable)
- perhaps improve the existing functions (kill_python() does a strange dance instead of calling communicate() on the subprocess.Popen object, is there a reason for that?)
- convert most uses of subprocess.<some_func>([sys.executable, ...]) in the test suite to use script_helper instead

This was suggested by Nick in issue477863.
History
Date User Action Args
2010-08-04 22:50:47pitrousetrecipients: + pitrou, ncoghlan, ezio.melotti
2010-08-04 22:50:47pitrousetmessageid: <1280962247.74.0.724550733964.issue9517@psf.upfronthosting.co.za>
2010-08-04 22:50:46pitroulinkissue9517 messages
2010-08-04 22:50:45pitroucreate