Re: [Python-Dev] [Python-checkins] devguide: Start a doc on running and writing unit tests.
+The shortest, simplest way of running the test suite is:: + + ./python -m test
Not on Windows. C:\Programs\Python32>./python -m test '.' is not recognized as an internal or external command, operable program or batch file. python -m test works (until it failed, separate issue). I would like to know, insofar as possible, how to run tests from the interpreter prompt (or IDLE simulation thereof) from whatmod import whatfunc; whatfunc() # ?? ditto for such remaining alternatives you give as can be made from prompt. 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. --- Terry Jan Reedy
On Wed, 05 Jan 2011 17:43:32 -0500 Terry Reedy <tjreedy@udel.edu> wrote:
Not on Windows. C:\Programs\Python32>./python -m test '.' is not recognized as an internal or external command, operable program or batch file.
python -m test works (until it failed, separate issue).
This will not run the right interpreter, unless this is an installed build. You must use: - "PCbuild\python_d.exe" in debug mode - "PCbuild\python.exe" in release mode - "PCbuild\amd64\python_d.exe" in 64-bit debug mode - "PCbuild\amd64\python.exe" in 64-bit release mode
I would like to know, insofar as possible, how to run tests from the interpreter prompt (or IDLE simulation thereof)
You can't. There is no such supported thing. Regards Antoine.
On Jan 5, 2011 4:45 PM, "Terry Reedy" <tjreedy@udel.edu> wrote:
+The shortest, simplest way of running the test suite is:: + + ./python -m test
Not on Windows. C:\Programs\Python32>./python -m test '.' is not recognized as an internal or external command, operable program or batch file.
python -m test works (until it failed, separate issue).
I would like to know, insofar as possible, how to run tests from the
interpreter prompt (or IDLE simulation thereof)
from whatmod import whatfunc; whatfunc() # ??
ditto for such remaining alternatives you give as can be made from prompt.
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.
--- Terry Jan Reedy
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) :) 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.
On 1/5/2011 5:57 PM, Antoine Pitrou wrote:
On Wed, 05 Jan 2011 17:43:32 -0500 Terry Reedy<tjreedy@udel.edu> wrote:
Not on Windows. C:\Programs\Python32>./python -m test
Installation, not checkout.
'.' is not recognized as an internal or external command, operable program or batch file.
python -m test works (until it failed, separate issue).
This will not run the right interpreter, unless this is an installed build.
It is, from 32b2.msi. I have no compiler ;-). -- Terry Jan Reedy
On Thu, 06 Jan 2011 00:34:11 -0500
python -m test works (until it failed, separate issue).
This will not run the right interpreter, unless this is an installed build.
It is, from 32b2.msi. I have no compiler ;-).
Ah, sorry. For the devguide, however, I recommend assuming an uninstalled up-to-date build, since keeping fresh sources is the most productive way (or the least frustrating) way of contributing. Note that, if you're willing to give it a try, Microsoft Visual Studio Express is a free download (free as in beer). Regards Antoine.
participants (3)
-
Antoine Pitrou -
Brian Curtin -
Terry Reedy