On Sun, Aug 1, 2010 at 11:55 PM, Nick Coghlan <ncoghlan at gmail.com> wrote: ... > Is dealing with name conflicts left up to the application? When an application iterates on the plugins that are supposely built for it, it will probably expect a single type of object. For instance unitest2 will want classes that are overriding its Plugin base class. So it should be able to drop objects that are not compliant with its system. Now, since the distutils id at PyPI is unique, using it for the application name in the plugin like I proposed, should also help preventing this issue.
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