[TIP] Guidelines for where to put tests & how to package them

[C. Titus Brown]

On Fri, Feb 26, 2010 at 07:36:59PM +0000, Michael Foord wrote:
>> test command performs test discovery (as a last recourse AFAICR, /me
>> cc-ing to P.J. Eby because probably he has further updates ;o) using a
>> loader: setuptools.comand.test.xxx
>>    
> I'd rather follow up with Tarek (cc'd) as the lead maintainer of both  
> distribute (the maintained fork of setuptools) and of distutils(2).

Aieeee, I'm trying to come up with a sensible convention BEFORE we bring
it to the stdlib people ;).

>> so it would be very nice when defining packaging
>> conventions, layout ... not to enforce the use of that protocol, so
>> that if another discovery is used then it could still be compatible
>> with the more abstract good practices. (all this said from my selfish
>> position, I confess)
>
> Yes, but get_suite/test_suite is not supported, so distutils2 still  
> *should* use a unittest supported protocol. Probably Tarek and I need to  
> discuss how the setup.py test command should work for distutils2. It  
> should support non-unittest tests as well (I guess?) so specifying a  
> unittest suite is not necessarily ideal.

YES, please let's support non-unittest tests.

> 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.

Really?  And that's at the BOTTOM of your e-mail? :)

--titus
-- 
C. Titus Brown, ctb at msu.edu