On Tue, Aug 11, 2009 at 8:02 AM, Martijn Faassen<faas...@startifact.com> wrote:
> Jim Fulton wrote:
>> Id like us to say something along the lines of:
>> "If your tests have additional dependencies, define "test" extra with
>> these dependencies. Also define tests_require and test_suite so that
>> your package supports the test command."
>> (Not verbatim and we should give examples.)
>> Note I used to object to tests_require because the information wasn't
>> available after installation. I still do, but I've started using it
>> anyway. Tres wrote a plugin to fix this (thanks Tres), but I think
>> it's easier just to define tests_require (and test suite) along with
> Ah, that's cool. I take it it's not yet possible to do without the test
> extra entirely and let buildout rely on the test_require section? That
> way we could do without duplication.
That's what Tres' setuptools plugin allows. It seems to me to be less
work to just repeat the information. Even then, you don't really have
to repeat it.
You can define the test requirements as a module-level variable and
then refer to the variable in both tests_require and the extras
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -