[Grok-dev] grokproject/buildout problems

Maurits van Rees m.van.rees at zestsoftware.nl
Mon Sep 22 11:38:26 EDT 2008


Uli Fouquet, on 2008-09-22:
> This should be fixed with a new `grokproject` release due to the switch
> to `z3c.recipe.i18n` :-)

I am not sure about that recipe.  At least the bin/i18nstats stopped
working after I did an i18nmergeall (no languages were reported) and
i18nmergeall itself did not mark a translation as fuzzy.  But perhaps
the lovely recipe has the same problem; not checked.

> With introduction of `eggbasket` we started to call
> `zc.buildout.buildout.main()` several times in `grokproject`.
> Unfortunately `zc.buildout` adds a new logging handler (stream to
> `sys.stdout`) each time it is called (and does not remove it after the
> work is done). As a result we get every buildout message two or three
> times, depending on the amount of times `buildout.main()` was called
> before.
>
> I added a function to remove those leftover handlers 'manually', which
> fixes that behaviour of duplicated lines. The fix might of course be
> improvable.

Looks fine to me.  Thanks!

> After downloading `zc.buildout` and installing `eggbasket` in
> `grokproject` we run buildout with the '-q' option. Maybe we should make
> the output visible? Or at least respect any verbosity options passed to
> buildout?

Fixed: we now respect the verbosity.

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]



More information about the Grok-dev mailing list