For Pynie we're developing a bootstrapping test suite, which may be
useful to other implementations as they migrate to 3.x. It uses Robert
Collins' SubUnit, which decouples the testing framework from the tests.
So the testing framework runs in CPython (or any reasonably complete
Python 2.x implementation), while the tests run in Pynie. All that's
required to pass the first test is an implementation of 'print' and
string constants. The tests gradually build up in complexity through
…
[View More]numeric constants, operators, control structures, functions, etc, and
when we're done with them will walk all the way through to supporting
the full Python 3.x syntax. When the bootstrap is complete, the test
framework moves to Pynie too, integrated with the core CPython test suite.
It might eventually be useful to add to the py3k branch, though I
wouldn't include it in release tarballs. Or, if another repo is started
for the benchmark tests, the bootstrapping tests might be added there.
We'll contribute it to the PSF, anyway, so it's available. It does
depend on SubUnit, which isn't part of the standard library. I can strip
it down to a minimal subset of SubUnit's features and include them in
the test running script if that makes it more generally useful.
Right now the tests live in Lib/test/parrot in the Pynie repository, but
will likely move to Lib/test/bootstrap (suggestions on Python-friendly
naming welcome).
Allison
[View Less]
On Sat, Apr 4, 2009 at 11:52 AM, Collin Winter <collinw(a)gmail.com> wrote:
> On Sat, Apr 4, 2009 at 7:33 AM, Michael Foord <fuzzyman(a)voidspace.org.uk> wrote:
>> Antoine Pitrou wrote:
>>>
>>> Nick Coghlan <ncoghlan <at> gmail.com> writes:
>>>
>>>>
>>>> C. Titus Brown wrote:
>>>>
>>>>>
>>>>> I vote for a separate mailing list -- 'python-tests'? -- but I don't
>>&…
[View More]gt;>> know exactly how splintered to make the conversation. It probably
>>>>> belongs at python.org but if you want me to host it, I can.
>>>>>
>>>>
>>>> If too many things get moved off to SIGs there won't be anything left
>>>> for python-dev to talk about ;)
>>>>
>>>
>>> There is already an stdlib-sig, which has been almost unused.
>>>
>>>
>>
>> stdlib-sig isn't *quite* right (the testing and benchmarking are as much
>> about core python as the stdlib) - although we could view the benchmarks and
>> tests themselves as part of the standard library...
>>
>> Either way we should get it underway. Collin and Jeffrey - happy to use
>> stdlib-sig?
>
> Works for me.
Me too.
bcc python-dev, -> stdlib-sig
First question: Do people want the unladen-swallow performance tests
in the CPython repository until the whole library gets moved out? If
so, where? Tools/performance? Lib/test/benchmarks?
Jeffrey
[View Less]