[Grok-dev] Re: buildout and download errors

Martijn Faassen faassen at startifact.com
Thu Aug 16 12:43:32 EDT 2007

On 8/16/07, Uli Fouquet <uli at gnufix.de> wrote:

> > Okay, this is a problem with the current approach. I didn't realize
> > when I told JW to go ahead with this that someone was depending on it
> > besides Grok yet.
> No worries! The code wasn't checked in at that time. And it's easy to
> write an own package finder if needed.

scan is intended to be a generic functionality so nobody will have to
write one ever again. :)
(we looked for one while writing grok but couldn't find one)

> > Why don't you roll back this behavior from martian's scan, or at least
> > make it optional (pass a list of modules names to ignore to it, or a
> > filter function, or something like that). If you have time?
> I'd do the latter with a filter function tonight if that's okay for
> everybody.
> The tests problem might be solved more easily (and more explicitly) with
> the upcoming grok.testing.

Not sure how it would help - the idea is that grok doesn't actually
grok anything defined in test and ftests modules. Comes to mind, this
directly conflicts with having grok pick up tests, though it'll
probably be another run anyway.



More information about the Grok-dev mailing list