Chris Withers wrote:
> Nick Coghlan wrote:
>> My personal preferences:
>>
>> Thorough: ./python -m test.regrtest -uall
>> Typical: ./python -m test.regrtest
>> Specific: ./python -m test.regrtest test_mod1 test_mod2
>
> This looks good, I assume this would work on Windows too?
Yep - and of course
s...@pobox.com wrote:
>> My personal preferences:
>>
>> Thorough: ./python -m test.regrtest -uall
>> Typical: ./python -m test.regrtest
>> Specific: ./python -m test.regrtest test_mod1 test_mod2
Chris> This looks good, I assume this would work on Windows too?
I believe
>> My personal preferences:
>>
>> Thorough: ./python -m test.regrtest -uall
>> Typical: ./python -m test.regrtest
>> Specific: ./python -m test.regrtest test_mod1 test_mod2
Chris> This looks good, I assume this would work on Windows too?
I believe so, but you should stil
Nick Coghlan wrote:
My personal preferences:
Thorough: ./python -m test.regrtest -uall
Typical: ./python -m test.regrtest
Specific: ./python -m test.regrtest test_mod1 test_mod2
This looks good, I assume this would work on Windows too?
cheers,
Chris
--
Simplistix - Content Management, Zope
Georg Brandl wrote:
> Chris Withers schrieb:
>> Hi All,
>>
>> I found the very brief snippet on test-running at:
>>
>> http://python.org/dev/faq/#how-to-test-a-patch
>>
>> so thought I'd ask here:
>>
>> - what's the canonical way to run "all the tests"?
>
> Assuming UNIXy OSes: make test, or i
Chris Withers schrieb:
> Hi All,
>
> I found the very brief snippet on test-running at:
>
> http://python.org/dev/faq/#how-to-test-a-patch
>
> so thought I'd ask here:
>
> - what's the canonical way to run "all the tests"?
Assuming UNIXy OSes: make test, or if you want to save a bit of tim
Hi All,
I found the very brief snippet on test-running at:
http://python.org/dev/faq/#how-to-test-a-patch
...so thought I'd ask here:
- what's the canonical way to run "all the tests"?
- what's the canonical way to run the tests for just the package being
patched? (I'm assuming it's a standa
