Jim Fulton wrote:
On Tue, Aug 11, 2009 at 8:02 AM, Martijn Faassenfaas...@startifact.com
wrote:
[snip]
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
Hey,
Jim Fulton wrote:
[snip]
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
On Tue, Aug 11, 2009 at 8:02 AM, Martijn Faassenfaas...@startifact.com wrote:
Hey,
Jim Fulton wrote:
[snip]
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
Hey,
Fabio Tranchitella wrote:
[snip]
In zope.component we use tests_require, in the very same way, for example.
Shall I remove it there, too? Is there a policy/document which explains how
we use extras and tests_require?
Probably not. I think it'd be very good to add something like this to
On Sat, Aug 8, 2009 at 1:33 PM, Martijn Faassenfaas...@startifact.com wrote:
Hey,
Fabio Tranchitella wrote:
[snip]
In zope.component we use tests_require, in the very same way, for example.
Shall I remove it there, too? Is there a policy/document which explains how
we use extras and