From: <zia...@gm...> - 2007-12-07 09:20:02
|
Hanno Schlichting-2 wrote: >=20 > I wouldn't call this 'avoiding'. This is the only sane approach for > installing i18ndude 3.x. In an eggified world using one Python for > multiple things is a recipe for disaster. I was meaning to document this > more clearly in the installation notes but haven't found the time to do > it. This undocumented change in installation procedure is the last thing > on my list that needs to be fixed before I'll release a first 3.x > non-beta release ;) >=20 Ok Hanno Schlichting-2 wrote: >=20 >> but is there a "zope2-compatible" version of i18dude that woudl rely=20 >> on the same egg versions than the Zope 2.X code source has ? >=20 > What would those versions be? The ones for Zope 2.8.3 or 2.9.0 or 2.10.5 > or 2.11a1? They all use different versions of Zope 3.x. I'm afraid there > is no way around using proper sandboxes in Python anymore. >=20 Well that's because we were thinking about using it within a package to automate some i18n tasks =C3=A0 la PTS. So it means removing some eggs in the eggs/ directory after installation if i18ndude is added as a buildout dependency. (The same thing was happening with z3c.sqlalchemy which gets most zope.* pazckages. This was more problematic since it is more likely to be used in a product) =20 ++ Tarek --=20 View this message in context: http://www.nabble.com/i18ndude-dependencies-a= nd-Zope-2-installs-tf4956504s6748.html#a14209243 Sent from the Internationalization mailing list archive at Nabble.com. |