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

Terry Reedy tjreedy at udel.edu
Wed Apr 12 05:49:05 CEST 2006

"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?

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

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 

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

Terry Jan Reedy

More information about the Python-3000 mailing list