Message248895
| Author |
Jim.Jewett |
| Recipients |
Jim.Jewett, The Compiler, ezio.melotti, martin.panter, mbussonn, ncoghlan, njs, serhiy.storchaka, takluyver, terry.reedy |
| Date |
2015年08月20日.16:09:02 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1440086942.46.0.875676058108.issue24294@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Instead of using python directly in a subprocess, try calling a shell command that in turns calls python. (Admittedly, this may look like the pipe scenario...)
In theory, you could even drive another python interactively, using a GUI runner, but I'm not sure how much new infrastructure that would add to the test suite, so it might not be worth it.
I'm not aware of a list of manual tests (though perhaps there *should* be one...); I would put it under the DeprecationWarning docs, sort of like an example. Others may have better ideas. |
|