[Distutils] buildout, zc.recipe.testrunner and tests_require

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Phillip J. Eby wrote:
> At 11:35 AM 11/15/2007 -0500, Tres Seaver wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Jim Fulton wrote:
>>> On Mar 11, 2007, at 11:08 AM, Nathan R. Yergler wrote:
>>> ...
>>>> I tried using zc.recipe.testbrowser, thinking that maybe it'd look at
>>>> the tests_require for the target eggs, but no such luck.
>>> The tests_require option is only visible to the setup script.  It
>>> doesn't cause any data to be included in egg info.  It is an
>>> attractive nuisance IMO.
>> I hope the attached patch (against the head of the setuptools 0.6
>> branch) makes it less of a nuisance.  The patch adds an egg-info file
>> entry point which writes the 'tests_require' value to a fill in the
>> .egg-info directory.
> 
> Interesting, and worth considering.  Meanwhile, note that you can 
> also distribute this as a plugin, or register the entry point in 
> zc.buildout.  That is, you don't need this to be a patch in order to 
> get the same behavior in a given Python installation.

Thanks, I realized that I could distribute it separately about 3 seconds
after hitting "Send". :)

I just uploaded 'eggtestinfo-.0.1.tar.gz' to the cheeseshop.  It exports
both the 'test_suite' and the 'tests_require' information to a single
'test_info.txt' file.



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPH2E+gerLs4ltQ4RAmUYAJ9xv6ounUdYV8FY1IIA3aNuGXCulQCfZTrh
Y4FIeBAYP+dEGkwAMLuRw6s=
=83wG
-----END PGP SIGNATURE-----