Dino Viehland wrote:
Mark wrote:
On Wed, Sep 23, 2009 at 4:54 PM, Dino Viehland <di...@microsoft.com> wrote:
We are going to start contributing tests back real soon now. I'm not sure
that these are the best tests to contribute as they require a version of
Python to compare against rather than being nice and stand alone. But I'm
sure we have other tests which cover this as well just not as exhaustively.
We could also possibly check in the baseline file and then CPython could
compare it's self to previous versions but it'd probably be a pretty
big file - so it probably shouldn't be included in the standard install
in the tests directory.
How big is big? For comparison, CPython's Lib/test/decimaltestdata
directory alone is already over 4Mb, so maybe size isn't an issue?
Running all of the side by side tests except our exceptions test it's
about 73Mb. It might be highly compressible though.
It sounds like many of these belong in an 'implementation-compliance'
test suite separate from the main test suite.
On the other hand many of the tests probably cover areas that are really
'sparsely' covered by current Python tests. For many of them getting a
'defined' set of results and changing the tests to compare against that
rather than against CPython could be really useful - but probably a lot
of work to create.
Michael
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
