[Python-Dev] proto-pep: plugin proposal (for unittest) (original) (raw)

Tarek Ziadé ziade.tarek at gmail.com
Fri Jul 30 20:19:14 CEST 2010

On Fri, Jul 30, 2010 at 5:54 PM, Éric Araujo <merwok at netwok.org> wrote:

It has an API, but the plugins are not interface based (so interface requirements don't need to be part of the plugin system). Oh, I see. With duck-typing and ABCs, I don’t make a difference between protocols and interfaces in my head :) Also, the I in API does mean interface, but not imply bondage-and-discipline interface systems.

PEP 376 is very promising for this part - well at least if the PLUGINS stuff becomes part of PEP 376, it doesn't seem to be mentioned at all at the moment. The dist-info directory introduced by PEP 376 will certainly be reused. Not sure if Tarek will want to edit PEP 376 (already accepted) to add plugins in metadata (provides-dist is in metadata, so having plugins here can make sense), or start a new PEP about a new concept in a new file.

What we want to do I think is to make dist-info a place when any file can be added, besides the ones described in PEP 376, then build the plugins proposal on this

Regards

Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com

-- Tarek Ziadé | http://ziade.org

More information about the Python-Dev mailing list