On Wed, Mar 05, 2008 at 05:01:53PM -0500, Tres Seaver wrote:
> Marius Gedminas wrote:
> > On Tue, Mar 04, 2008 at 05:03:13PM -0500, Tres Seaver wrote:
> >> I would think that getting 'python setup.py test' to work for each
> >> package-being-tested, which a) makes sure that the package works even
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Gedminas wrote:
> On Tue, Mar 04, 2008 at 05:03:13PM -0500, Tres Seaver wrote:
>> Marius Gedminas wrote:
>>
>>> Also, I think that lack of a bin/test for any package can be rightly
>>> considered to be a bug.
>> 'bin/test' doesn't make much sens
Tres Seaver wrote:
I would think that getting 'python setup.py test' to work for each
package-being-tested, which a) makes sure that the package works even
for non-buildout-aware users, and b) fits what everybody else in the
Python eggs word expects.
+1
Chris
--
Simplistix - Content Managemen
On Tue, Mar 04, 2008 at 05:03:13PM -0500, Tres Seaver wrote:
> Marius Gedminas wrote:
>
> > Also, I think that lack of a bin/test for any package can be rightly
> > considered to be a bug.
>
> 'bin/test' doesn't make much sense to me as a way to run the tests
> belonging to the packge-being-teste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Gedminas wrote:
> Also, I think that lack of a bin/test for any package can be rightly
> considered to be a bug.
'bin/test' doesn't make much sense to me as a way to run the tests
belonging to the packge-being-tested: it corresopnds to the te