[Python-3000] Separating out CPython and core Python tests

[Guido van Rossum]

On 4/12/06, Terry Reedy <tjreedy at udel.edu> wrote:
>
> "Guido van Rossum" <guido at python.org> wrote in message
> > I agree that such a test suite would be helpful. I don't think it
> > should wait for Python 3000.
>
> Possible plan:
>
> Add 'spec' or 'specification' or 'language', 'implementation', and possibly
> 'support' subdirs to ...Lib/test.  Put most test files in 'spec', possibly
> support files in 'support' and any implementation-only tests in
> 'implementation'.  Test_peepholer.py at least would go in the latter.
> Should tests for C-coded modules go here too?

Perhaps. I suggest taking this to python-dev; I don't think we need to
wait until 3.0 to do this.

> Unless done immediately for 2.5, do this for trunk (future 2.6) only after
> 2.5 maintenance branch established.

It would probably slow down the 2.5 release; let's do it for 2.6.

> Adjust 'from test.something import ...' statements to 'from
> test.subdir.something import ...' with Python script.
>
> Split a few files known to have implementation tests, such as the test
> somewhere that small ints up to a certain size are preallocated.  This
> could break even for a customized CPython build.  Would having tests like
> this segregated in an implementation test directory help even CPython
> customizers?

I doubt that that particular customization (or any other, really) is
ever invoked -- these are customizable so we can tweak it in future
implementations.

> As Michael suggested, let Jython, IronPython, and PyPy people suggest
> additional file splits or movements.

More reason to invoke python-dev.

(I also like Brett's idea of using decorators to provide fine-grained
annotations rather than having to split everything across to multiple
files according to scope. It's quite possible that some test are moved
between categories in the future. Not that I'm against splitting
across files if there's a clear separation.)

--
--Guido van Rossum (home page: http://www.python.org/~guido/)