On Mon, Aug 2, 2010 at 3:06 AM, P.J. Eby <p...@telecommunity.com> wrote: .. > > So without specific examples of why this is a problem, it's hard to see why > a special Python-specific set of configuration files is needed to resolve > it, vs. say, encouraging application authors to use the available > alternatives for doing plugin directories, config files, etc.
I don't have a specific example in mind, and I must admit that if an application does the right thing (provide the right configuration file), this activate feature is not useful at all. So it seems to be a bad idea. I propose that we drop the PLUGINS file idea and we add a new metadata field called Provides-Plugin in PEP 345, which will contain the info I've described minus the state field. This will allow us to expose plugins at PyPI. IOW, have entry points like setuptools provides, but in a metadata field instead of a entry_points.txt file. Tarek -- Tarek Ziadé | http://ziade.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
