On Sun, Aug 1, 2010 at 10:37 PM, Tarek Ziadé email@example.com wrote:
Here's a proposal to extend PEP 376 to support a basic plugins feature -- you should read PEP 376 before reading this mail
It's basically Phillip's entry points, but with an activation flag, and a per-user config file.
= adding a PLUGINS file =
A new file called 'PLUGINS' is added to the dist-info directory at install time, and contains a list of plugins for the installed distribution.
After some more thoughts, ISTM that it would be better to have the plugin definitions in a new metadata field in PEP 345, rather than in the PLUGINS file. The reason is that it will allow tools and users to browse PyPI to look for plugins.
The PLUGINS file can be kept only for the state value, which is not read-only.