regebro at gmail
Apr 28, 2010, 2:20 PM
Post #2 of 2
(379 views)
Permalink
|
On Wed, Apr 28, 2010 at 17:00, Jim Pharis <binbrain [at] gmail> wrote:
> We are currently on Zope 2.9.6 and we are working on upgrading but it isn't
> going to happen anytime soon. I'm trying to use a package that is depending
> on a few newer component architecture packages; zope.component,
> zope.interface... Even though zope.component and zope.interface hadn't been
> egged in 2.9.6, Zope Products seem to import from zope.component in Python
> lib instead of zope/component in the Zope.
Yes, you can not easily have different packages in different parts of
the same process. It's theoretically possible, but difficult and will
likely break in unexpected ways. In general, once you have imported a
package subsequent packages will use the same one.
> Is there any clean way to isolate the newer packages?
Run different python interpreters.
--
Lennart Regebro: http://regebro.wordpress.com/
Python 3 Porting: http://python-incompatibility.googlecode.com/
+33 661 58 14 64
_______________________________________________
Zope maillist - Zope [at] zope
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
|
