Barry Warsaw wrote:
> I think I'm being affected by this same bug. If I put my top-level
> package directory next to my setup.py file, and I let buildout put the
> eggs in its standard place, bin/test will fail. See this thread:
Yup, that's the one.
You'll also get the same problem if you build that package into an egg
and then try and run the tests.
I currently work around this by having buildout use an egg cache
elsewhere specified in my default.cfg(C:\buildout-eggs in my case) which
has other advantages in that lots of buildouts need the same eggs, and
they only need to be downloaded once.
I work around the build problem by building eggs on one machine and
running tests on another.
> Note that if I put the eggs elsewhere, or if I put my mailman directory
> under a src directory, then there's no problem.
Yeah, but I hate that pattern, and it sounds like you're not fond of it
either ;-)
Barry Warsaw wrote:
> I think I'm being affected by this same bug. If I put my top-level
> package directory next to my setup.py file, and I let buildout put the
> eggs in its standard place, bin/test will fail. See this thread:
Yup, that's the one.
You'll also get the same problem if you build that package into an egg
and then try and run the tests.
I currently work around this by having buildout use an egg cache cfg(C:\ buildout- eggs in my case) which
elsewhere specified in my default.
has other advantages in that lots of buildouts need the same eggs, and
they only need to be downloaded once.
I work around the build problem by building eggs on one machine and
running tests on another.
> Note that if I put the eggs elsewhere, or if I put my mailman directory
> under a src directory, then there's no problem.
Yeah, but I hate that pattern, and it sounds like you're not fond of it
either ;-)
cheers,
Chris
-- www.simplistix. co.uk
Simplistix - Content Management, Zope & Python Consulting
- http://