system path should be ignorable/overridable
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.
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.
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. The latter option would not break people's expectations: their system-installed packages that the buildout doesn't override will continue to be importable.
|Florian Friesdorf (flow-mytum) wrote : system path should come last (was Re: system path should be ignorable/overridable)||#5|
|Andi Zeidler (witsch) wrote : Re: [Bug 158756] system path should come last (was Re: system path should be ignorable/overridable)||#8|