[New-bugs-announce] [issue25588] Run test suite from IDLE idlelib.run subprocess

Terry J. Reedy report at bugs.python.org
Mon Nov 9 03:04:43 EST 2015


New submission from Terry J. Reedy:

This issue proposes stress testing idlelib.run by running code that already reports whether results are as expected or not -- the test_suite.  Since this one test will take at least as long as the test suite, and will probably need human intervention anyway, it would not be part of test_idle, but would be run separately manually, like htest.

IDLE runs user code in a user process started with subprocess.POpen(executable + 'path/to/idlelib/run.py' + args + user_code_path) (with user_code_path omitted for shell restarts).  When run from the editor, the intent is to imitate 'python -i user_code_path'.

On python list, someone reported that running a program using pyqt5 (and qt5) hung on exit while running with python3 (on Ubuntu, no -i) worked.  I have asked for more details, including whether it works with -i included.  In the meanwhile, I wondered ...

While the run module might not be able to run programs with certain 3rd party imports, can it at least run programs restricted to stdlib imports and well enough behaved to run with python -i.  (A programs that, for instance, disables standard i/o streams would fail both in IDLE and with python.)  A test would be to at least run all stdlib tests, with the same result, as run otherwise on the same system.  The tests should be run in the user process itself and not in additional processes.  They could be run either all in one process or each in a new run process.

If successful, I will put code and instructions in a new idlelib/idle_test/rtest.py/txt.

----------
assignee: terry.reedy
components: IDLE, Tests
messages: 254371
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Run test suite from IDLE idlelib.run subprocess
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25588>
_______________________________________


More information about the New-bugs-announce mailing list