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

Michael Foord fuzzyman at voidspace.org.uk
Sat Jul 31 18:35:07 CEST 2010

On 31/07/2010 17:22, Tarek Ziadé wrote:

On Sat, Jul 31, 2010 at 1:46 PM, Michael Foord <fuzzyman at voidspace.org.uk> wrote: ...

Installation of plugins would still be done through the standard distutils(2) machinery. (Using PEP 376 would depend on distutils2. I would be fine with this.) Note that the PEP 376 implementation is mainly done in pkgutil. A custom version lives in distutils2 but when ready, will be pushed independently in pkgutil

Ok. It would be helpful for unittest2 (the backport) if it was still available in distutils2 even after the merge into pkgutil (for use by earlier versions of Python). I guess you will do this anyway for the distutils2 backport itself anyway... (?)

All the best,

Michael Foord

Regards Tarek

-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

More information about the Python-Dev mailing list