Stuart Bishop wrote:
silence it (and open a bug report at the same time). The noisier test output
is, the more likely you are to miss relevant information.
Totally agreed, I was kinda shocked at how many deprecation errors Zope
2.9 ships with :-(
Chris
--
Simplistix - Content Management, Zo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> Philipp von Weitershausen wrote:
>
>> Tres Seaver wrote:
>>
>>> I'm not sure what Chris meant, but the change to the visual output of
>>> the testrunner when running "with dots" seems gratuitous to me, as well
>>> -- I don't see
Martijn Faassen wrote:
Anyway, a release and the development situation looking similar helps
people actually work on the same codebase and structure, and not having
to learn different ways of doing things as soon as they switch. Forcing
context switches on people isn't a good idea.
Huge +1 fr
Philipp von Weitershausen wrote:
Tres Seaver wrote:
I'm not sure what Chris meant, but the change to the visual output of
the testrunner when running "with dots" seems gratuitous to me, as well
-- I don't see any benefit to the "indented, narrower" output,
Me neither, for what it's worth.
Ok
Stephan Richter wrote:
On Tuesday 21 March 2006 02:54, Chris Withers wrote:
I particularly hate the fact that no real effort was put into backwards
compatibility, not to mention those silly weird
sort-of-fifty-dots-per-line thing that doesn't actually work.
I think this is not fair. Jim has tr
On Wed, Mar 22, 2006 at 06:25:41PM +0100, Martijn Faassen wrote:
> Anyway, a release and the development situation looking similar helps
> people actually work on the same codebase and structure, and not having
> to learn different ways of doing things as soon as they switch. Forcing
> context s
Jim Fulton wrote:
From the old testrunner, which I miss *a lot*, I could ensure I am
indeed running a specific module by doing...
Yup, this is one of the things I like least from the Zope 3 world.
What happened to proposals and community agreement before inflicting
big changes on other peopl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What's really depressing about this is that we are spending
so much energy and angst over the layout of dots.
That's probably because it is perceived as "yet another thing that
has randomly changed/was broken fin 2.9". The "energy and angst" is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Mar 2006, at 06:15, Philipp von Weitershausen wrote:
I still don't understand why people whine about "make install" being
gone. The point of a checkout is that you have a full functional SVN
working copy, not an installation source. If you wan
Tres Seaver wrote:
> I'm not sure what Chris meant, but the change to the visual output of
> the testrunner when running "with dots" seems gratuitous to me, as well
> -- I don't see any benefit to the "indented, narrower" output,
Me neither, for what it's worth.
> Zope 2.9 broke the 'confiugre-ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Chris Withers wrote:
>
>> Jens Vagelpohl wrote:
>>
>>>
>>> From the old testrunner, which I miss *a lot*, I could ensure I am
>>> indeed running a specific module by doing...
>>
>>
>>
>> Yup, this is one of the things I like least
Jens Vagelpohl wrote:
From the old testrunner, which I miss *a lot*, I could ensure I am
indeed running a specific module by doing...
Yup, this is one of the things I like least from the Zope 3 world. What
happened to proposals and community agreement before inflicting big
changes on other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm working on CMFCalendar and running the tests out of the instance
home like this:
bin/zopectl test -m CMFCalendar -vv
This runs tests, according to the output, but apparently not how or
where I think it should. No .pyc files appear in the te
13 matches
Mail list logo
