Tres Seaver wrote:
> My major beef with zc.buildout is perhaps actually a problem with the
> recipes nearly everybody uses: they blow away hand-edited stuff without
> warning. In particular, changes to things like the zope.conf file get
> zapped, because buildout (or the recipe) thinks that the f
Noah Gift wrote:
> In reference to this rather long discussion. I would love to get an
> interview or case study on buildout in the scope of package management
> for Python for the book I am co-authoring on Python For *nix Systems
> Administration. If there is an official ambassador, I woul
Marius Gedminas wrote:
> It's not a problem with the recipe, it's a problem with zope.testing, or,
Sorry, that should have been obvious to me. No idea what made me blame it
on the recipe...
> more fundamentally, with Python. The sys.settrace hook used to
> implement coverage tracing is non-recu
On Tue, Feb 12, 2008 at 02:28:21PM +0100, Thomas Lotze wrote:
> I've noticed a bug which is most probably the fault of
> zc.recipe.testrunner, and as I'm not sure where to report bugs against
> this buildout recipe, I'll drop a note here.
>
> The problem occurs when checking test coverage using the
I've noticed a bug which is most probably the fault of
zc.recipe.testrunner, and as I'm not sure where to report bugs against
this buildout recipe, I'll drop a note here.
The problem occurs when checking test coverage using the test runner's
--coverage option. I've run bin/test --coverage on a sui
