When adding a custom plugin with the same name as one already found by the
default plugin manager, the system plugin is used without any warning to the
user.
In the attached file, I implement a plugin named "Skip" that skips when
"MySkipTest" is raised. Since "Skip" is a built-in plugin already, raising
"MySkipTest" causes an exception. When the plugin is renamed to "MySkip",
everything works fine.
Possible solution: either warn the user when a plugin conflict is detected, or
prefer plugins added with ``addplugins``.
Original issue reported on code.google.com by sjvdw...@gmail.com on 30 Nov 2011 at 5:25
Original issue reported on code.google.com by
sjvdw...@gmail.com
on 30 Nov 2011 at 5:25Attachments: