[Python-Dev] PEP: Consolidating names and classes in the `unittest` module (updated 2008-07-15)
Terry Reedy
tjreedy at udel.edu
Thu Jul 17 00:46:59 CEST 2008
Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> If camelCase / duplicated names are such a pain, write a *new* module,
> 'unittest2', and port Python's tests to use it, thereby leaving the much
> larger volume of not-in-Python tests still working. One might then
> remove the 'unittest' module in a later release, packaging it as a
> standalone distibution for the projects which still need it.
There was, at one time at least, some degree of consensus for dropping
the Fail names and keeping the Assert names, which appear to comprise
75%-80% of usage 'in the wild'. There seems to less consensus on also
changing the Assert names from CamelCase to under_score versions. So I
was also thinking about a 'unittest2', recommended for new projects and
gradual changeover of the Python test suite. 'Unittest' could be left
unchanged but gradually disrecommended, deprecated, and removed (perhaps
in 4.0 if not before).
More information about the Python-Dev
mailing list