Benji York wrote:
It'd be nice to have a -C option that disables -c for when your test
runner has -c included in the default options (as I intend to do with mine).
I've added such an option. The -C switch makes sense, but I'm not
entirely happy with the --no-color version of the name, any
Hello Philipp,
Yep, had the same idea just yesterday. But how to keep the trunk also
in a good-consistent shape (if it needs to be kept in a good shape)?
Sunday, July 15, 2007, 3:07:17 PM, you wrote:
Adam Groszer wrote:
Did something at /repos/Zope3/branches/adamg-mechanize-update/,
the
Benji York wrote:
Marius Gedminas wrote:
There's a little complication: when you have test layers that don't
support tearDown, some of the tests are run in a subprocess, where
stdout isn't a terminal (it's a pipe), but all the output will be copied
verbatim to the stdout of the parent process
On Jul 13, 2007, at 5:09 PM, Wichert Akkerman wrote:
...
Amen. I find failing doctests to be much harder to debug as well.
Are you are of the post-mortem debugging features of the zope.testing
test runner? I find this helps a lot when debugging test failures.
On Jul 14, 2007, at 1:00
On Monday 16 July 2007 08:44, Jim Fulton wrote:
For me, post-mortem debugging or using set_trace is almost always
good enough. On those occasions where I really need to step through a
series of example, It's straightforward to convert them to a single
example.
Me too. Actually I only
On Sunday 15 July 2007 11:26, Benji York wrote:
I think I miscommunicated. Let me combine your example and mine to
demonstrate what I was talking about. Say you have an HTML document and
you want to make assertions about a portion of it. You could use XPath
to extract part of the document
On Sunday 15 July 2007 12:45, Marius Gedminas wrote:
I was talking about regular programmer-facing documentation and couldn't
find a good word for it (tutorial? programmer's guide). The thing you
read to learn about the package, not the thing you use to look up some
details of some function.
Stephan Richter wrote:
Okay, I am done preaching. ;-)
Preach on, brother!
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub:
Hello!
I've just looked at zope.app.basicskin.standardmacros and it seems to me
standard_macros/view (and similar macros) now not used and moreover some
templates now unaccessible through standard_macros for example
zope/app/rotterdam/view_macros.pt now overridden by
On 16 Jul 2007, at 08:59 , Adam Groszer wrote:
Yep, had the same idea just yesterday. But how to keep the trunk also
in a good-consistent shape (if it needs to be kept in a good shape)?
Well, that's a good question. If you'd like to update
zope.testbrowser on the trunk, I suppose you'd have
10 matches
Mail list logo
