Re: Switching from nose to unittest2 - how to continue after an error?

From	alex23 <wuwei23@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: Switching from nose to unittest2 - how to continue after an error?
Date	2014-08-26 11:10 +1000
Organization	A noiseless patient Spider
Message-ID	<ltgmr0$r35$1@dont-email.me> (permalink)
References	<CANc-5UwXqeSbzgBQbWXEvJu-3j1bY+RU76Hz0w36_QaGt+RBaA@mail.gmail.com> <CANc-5UwWVwtae1MQ34nWkGra8h007MccXxyDxnfBGvT52TBqvA@mail.gmail.com> <ltg129$oo1$1@ger.gmane.org> <CANc-5Ux7Xx-3YgtakySUkcusZYaW3s_1-CryD8TcHEP5HAnksA@mail.gmail.com> <mailman.13431.1408997567.18130.python-list@python.org>

Show all headers | View raw

On 26/08/2014 6:12 AM, Mark Lawrence wrote:
> Whatever happened to "There
> should be one-- and preferably only one --obvious way to do it."? :)

Ignoring for a moment that "one obvious way" only applies to 
Python-the-language, when it comes to libraries, there's a few factors 
(IMO) that affect this:

1. Some people find it easier to write something from scratch that read 
docs for an existing product.

2. It's easier to reimplement an existing concept than come up with 
something new.

This is actually a good thing, though, as monocultures die. Just chalk 
it up to evolutionary pressure :)

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Switching from nose to unittest2 - how to continue after an error? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-25 21:12 +0100
  Re: Switching from nose to unittest2 - how to continue after an error? alex23 <wuwei23@gmail.com> - 2014-08-26 11:10 +1000

csiph-web