[issue10572] Move unittest test package to Lib/test

Michael Foord report at bugs.python.org
Mon Nov 29 01:52:59 CET 2010


New submission from Michael Foord <michael at voidspace.org.uk>:

Having tests in Lib/test instead of inside the package makes it easier to grep the unittest package without grepping the tests. The Windows installer has an "install without tests" option which is easier to honour if the tests aren't in the package.

However, currently all packages that have test *packages* have the tests in the package rather than inside Lib/test. (There are no test packages inside Lib/test.)

Examples: email, distutils, ctypes, importlib, json, lib2to3, sqlite3

I also maintain an external port of unittest from Python 3. This is unittest2-py3k. Moving the tests would make it *slightly* harder to keep this in sync. I'm moving to maintaining this port as a set of patches rather than a separate branch. These patches can be applied automatically to unittest from py3k head. unittest2-py3k will be built automatically by a script, so it isn't a big deal.

----------
assignee: michael.foord
keywords: easy
messages: 122751
nosy: michael.foord
priority: normal
severity: normal
status: open
title: Move unittest test package to Lib/test
type: behavior
versions: Python 3.2

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10572>
_______________________________________


More information about the Python-bugs-list mailing list