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/081284.html below:

[Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement)

[Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement) [Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement)Ben Finney ben+python at benfinney.id.au
Thu Jul 17 00:52:41 CEST 2008
Michael Foord <fuzzyman at voidspace.org.uk> writes:

> Collecting testcases from the filesystem is a pain. But actually
> writing tests (including custom TestCases) using the unittest API is
> fine. I find unittest straightforward and readable, I like it.
> 
> I don't understand a lot of the criticism comes in for.

For my part, I wanted the redundancies removed and the PEP 8
conformance fixed as a precondition too *any* addition to the unittest
API.

Without those two (and the BDFL's pronouncement at the head of this
thread means they're not an option), I can't see the unittest API
getting anything except increasingly hideous and painful to use.

-- 
 \     “Never do anything against conscience even if the state demands |
  `\                                             it.” —Albert Einstein |
_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