Showing content from http://mail.python.org/pipermail/python-dev/attachments/20110105/94c33ff6/attachment.html below:
<p>On Jan 5, 2011 4:45 PM, "Terry Reedy" <<a href="mailto:tjreedy@udel.edu" target="_blank">tjreedy@udel.edu</a>> wrote:<br>
><br>
><br>
>> +The shortest, simplest way of running the test suite is::<br>
>> +<br>
>> + ./python -m test<br>
><br>
><br>
> Not on Windows.<br>
> C:\Programs\Python32>./python -m test<br>
> '.' is not recognized as an internal or external command,<br>
> operable program or batch file.<br>
><br>
> python -m test<br>
> works (until it failed, separate issue).<br>
><br>
> I would like to know, insofar as possible, how to run tests from the interpreter prompt (or IDLE simulation thereof)<br>
><br>
> from whatmod import whatfunc; whatfunc() # ??<br>
><br>
> ditto for such remaining alternatives you give as can be made from prompt.<br>
><br>
> Besides the convenience for Windows users (for whom the Command Prompt window is hidden away and possibly unknown), I think we should know if any tests are incompatible with interactive mode.<br>
><br>
> ---<br>
> Terry Jan Reedy</p><p><meta charset="utf-8"></p><p>The command prompt on Windows is no more hidden than it is on any other OS. In fact it's easier to find than on OS X (IMO) :)</p><p>I think we do need to make *some* assumptions in the developer docs that the reader is actually a developer (who would know where cmd is) and not a first-time user of the OS, otherwise it becomes a computer users guide and not a development guide.</p>
<p></p>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4