A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-July/081130.html below:

Consolidating names and classes in the `unittest` module (updated 2008-07-15)

[Python-Dev] PEP: Consolidating names and classes in the `unittest` module (updated 2008-07-15) [Python-Dev] PEP: Consolidating names and classes in the `unittest` module (updated 2008-07-15)Ben Finney bignose+hates-spam at benfinney.id.au
Tue Jul 15 12:31:46 CEST 2008
"Stephen J. Turnbull" <stephen at xemacs.org> writes:

> Ben Finney writes:
> 
>  > Removal of ``assert*`` names
>  > ----------------------------
>  > 
>  > There is no overwhelming consensus on whether to remove the
>  > ``assert*`` names or the ``fail*`` names;
> 
> 7 to 1 is overwhelming in my book.  See
> Message-ID: <loom.20080714T230912-310 at post.gmane.org>
> From: Antoine Pitrou <solipsis at pitrou.net>

That measured only usage of unittest *within the Python standard
library*. Is that the only body of unittest-using code we need
consider?

> While people's preferences are important, I think there is a very
> good case to made that keeping this much continuity in the test
> suite as possible is more so.

That's a separate argument, then. One which I don't dismiss, but it
needs to be stated as such.

-- 
 \           “A poet more than thirty years old is simply an overgrown |
  `\                                         child.” —Henry L. Mencken |
_o__)                                                                  |
Ben Finney

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4