[TIP] unittest2 plugins

Kumar McMillan kumar.mcmillan at gmail.com
Mon Jul 26 07:26:02 PDT 2010

Only tangentially related, but I believe this discussion spawned a
blog post from Tarek on implementing a generic plugin system for
Python.  Since I'm a fan of entry points and how they allow zero
config discovery of plugins, I like the proposal.  He's looking for
more feedback on the details:

On Mon, Jul 26, 2010 at 8:58 AM, jason pellerin <jpellerin at gmail.com> wrote:
> On Sat, Jul 24, 2010 at 5:39 AM, Michael Foord
> <fuzzyman at voidspace.org.uk> wrote:
>> On 24/07/2010 09:02, meme dough wrote:
>>> Hi,
>>> I see the email about unittest2 plugins.  I had a play with plugin
>>> mechanism.
>> This is *very* much an experimental work in progress. When it is a bit more
>> complete I will send an email to python-dev and this list describing the
>> mechanism and solicit feedback on it.
>> For those who just want to play now it is in the "plugins" branch of the
>> mercurial repo at:
>>    http://hg.python.org/unittest2
> This is quite encouraging! I had a look at the branch this weekend,
> and I can see pretty clearly how to implement most of nose's builtin
> plugins. The major exceptions are the multiprocessing plugin, which
> replaces the test runner, and nose's support for custom exception
> handling (like skiptest, but generalized -- in nose, skips are handled
> by a plugin that registers itself as the processor for SkipTest
> exceptions). Do you have any thoughts about how to support those kinds
> of plugins?
> I'm looking forward to working with this, it looks very flexible and clean.
> JP
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python

More information about the testing-in-python mailing list