Comment 1 for bug 158756

On Oct 30, 2007, at 1:05 PM, Martijn Faassen wrote:

> Public bug reported:
>
> The following problem keep biting the Grok project. We regularly get
> users who already have Zope 3 installed, or Twisted, or
> zope.interface,
> and so on, and as a result can't install and/or run Grok, due to the
> wrong packages appearing on the import either during recipe execution
> time, or during startup time.

It would be helpful if you could double check this. See below.

> We know people have to compile and install their own Python, but we
> can't expect beginning users to compile a custom Python (or even a
> virtual environment) just to try something out (on Windows and to a
> lesser extend MacOS the tools are likely not even installed to
> compile a
> custom Python). In one training session I ran into this problem with
> many of the participants, on 3 different platforms, Linux, Window and
> Mac OS X.

+1

> Having the ability to isolate a buildout entirely from site-packages
> would be very helpful, or alternatively let site-packages come last in
> the order.

Both seem reasonable.

> The latter option would not break people's expectations:
> their system-installed packages that the buildout doesn't override
> will
> continue to be importable.

Generated scripts always put eggs found at the start of the path.
buildout, like setuptools, searches site packages for eggs to install
and probably selects these some times, so I think this largely boils
down to the rules for finding eggs in the first place.

It would be helpful if you could verify this by verifying that, in
fact, the generated scripts have "system" eggs inserted by the script.

Jim

--
Jim Fulton
Zope Corporation