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/081141.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)Andrew Bennetts andrew-pythondev at puzzling.org
Tue Jul 15 15:05:33 CEST 2008
Ben Finney wrote:
> "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?

Three more data points then:

bzr: 13228 assert* vs. 770 fail*.

Twisted: 6149 assert* vs. 1666 fail*.

paramiko: 431 assert* vs. 4 fail*.

The data seems pretty overwhelmingly in favour of keeping assert*. 

-Andrew.

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