[Grok-dev] Wierd Thing: Grok Groping All Modules?
faassen at startifact.com
Sat May 23 16:40:34 EDT 2009
Jeff Rush wrote:
> Martijn Faassen wrote:
>> Ethan Jucovy wrote:
>>> Hmm, I think this is a bug in z3c.autoinclude. It's importing the
>>> locations to get their file paths so it can look for ZCML files to be
>>> included. But I *think* it could just as easily use
>>> pkg_resources.resource_filename (which is safe AFAIK) to get those
>>> paths. I'll try to double check that this change doesn't have any
>>> unintended consequences and put in the fix.
>> That'd be good to see, thanks!
>> I think in this case things were aggravated by the "from config import
>> *" bit in speechd.
> It is also interesting that I'm running it in a virtualenv --no-site-packages
> and buildout, and it -still- is reaching out to my system site-packages to
> find speechd. I can't seem to keep its hands off my site. ;-)
That is peculiar. I would suspect z3c.autoinclude again, but I don't
Ethan, can you replicate that behavior?
More information about the Grok-dev