Message137087
| Author |
eric.araujo |
| Recipients |
Trundle, bethard, eric.araujo, michael.foord, terry.reedy |
| Date |
2011年05月27日.17:04:09 |
| SpamBayes Score |
2.8738678e-12 |
| Marked as misclassified |
No |
| Message-id |
<1306515850.56.0.17771573161.issue11906@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Interactive mode is an approved method of running Python code, along
> with batch mode. The core interpreter and stdlib modules should run
> correctly in both modes. So the entire test suite should pass in both
> modes too.
You are right.
> That aside, the doc for test/ does not contain 'recommended' and does
> not discuss running a single test.
Such guidelines belong more in the devguide than the library doc: http://docs.python.org/devguide/runtests
> What I did is the easiest way on Windows.
I cannot argue with you on that :)
> In this case, following Andreas' remark, the bug is in the test, not
> the module, in that it miscalculates the expected output in the
> corner case of a null program name.
Since it’s an easy patch in the test file, +1. |
|