nose-devs/nose — Issue #460: Plugins included with addplugins keyword are overriden by builtin or third-party plugins registered with setuptools
Author: jpellerin
Created: 2011-12-14 16:12:00+00:00
State: open

What steps will reproduce the problem?
1. Create a new plugin with the same name as a builtin plugin (or a third-party plugin registered with setuptools)

2. Include your plugin in a nose testrun using the addplugins keyword:
nose.main(addplugins=[CustomPlugin()])

What is the expected output? What do you see instead?

I expected plugins a user explicitly includes with the addplugins keyword to take precedence over built-in or other third-party plugins. The opposite seems to be true. Setuptools-registered plugins override built-in plugins, which override addplugins.

Please use labels and text to provide additional information.

If you include plugins with the addplugins keyword, those plugins get added immediately with config.plugins.addPlugins(). Then, later on, when loadPlugins() is called as part of getParser(), the builtin plugins are loaded, as are third-party plugins registered using setuptools. Those plugins will overwrite any previously-added (from addplugins) plugins with the same name.

Google Code Info:
Issue #: 466
Author: BrendanM...@gmail.com
Created On: 2011-11-11T17:35:50.000Z
Closed On: 2011-11-11T18:04:25.000Z