Justin Ryan wrote:
On Tue, Jul 29, 2008 at 12:40 PM, Rob Miller <[EMAIL PROTECTED]> wrote:
more likely is that some other package that you have installed declared
zope.interface as a dependency, and a more recent version of zope.interface
was installed which is now conflicting w/ the one that your Plone version
installed. it's possible that this has happened at the system level. when
you created your virtualenv, did you use the --no-site-packages option?
Yeah, no, heh. We probably should consider that option, or at least
be a lot more careful with system-level site packages.
The challenge is, now that we have System Python 2.4 in RHEL5, and it
has RPMs for things like PIL and libxml2, it's convenient to use those
instead of reinstalling them into virtualenv, esp as they are not eggs
and seem actually to menially respect the virtualenv.
PIL has been packaged up as an egg by the repoze guys, at dist.repoze.org;
i've been using this for a bit and have been happy w/ it.
i'm not sure if there are any usable lxml2 eggs, but there are buildouts for
it, so if you're using buildout (IIRC you said you were) you can probably wire
it in that way.
-r
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2008/07/1217377308443
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
