i18ndude dependencies and Zope 2 installs

Hello,

i18dude depends on:

zope.tal >= 3.3
zope.interface >= 3.3
zope.i18nmessageid >= 3.3
zope.testing
elementtree

So after an easy_install, some zope 2.x won't work anymore
if they use the
same python,
since the code for zope.* is integrated and differs.

right now we use a virtualenv to avoid this, but is there a
"zope2-compatible" version of i18dude 
that woudl rely on the same egg versions than the Zope 2.X
code source has ?


Tarek

-- 
View this message in context: http://www.nabble.c
om/i18ndude-dependencies-and-Zope-2-installs-tf4956504s6748.
html#a14193884
Sent from the Internationalization mailing list archive at
Nabble.com.


------------------------------------------------------------
-------------
SF.Net email is sponsored by: The Future of Linux Business
White Paper
from Novell.  From the desktop to the data center, Linux is
going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Tarek Ziadé wrote:
> i18dude depends on:
> 
> zope.tal >= 3.3
> zope.interface >= 3.3
> zope.i18nmessageid >= 3.3
> zope.testing
> elementtree
> 
> So after an easy_install, some zope 2.x won't work
anymore if they use the
> same python,
> since the code for zope.* is integrated and differs.
> 
> right now we use a virtualenv to avoid this

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 ;)

> but is there a "zope2-compatible" version of
i18dude that woudl rely 
> on the same egg versions than the Zope 2.X code source
has ?

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.

Hanno

P.S. Personally I still use workingenv for i18ndude, so I
have a
'/opt/dude' sandbox and need to do 'source
/opt/dude/bin/activate' ones
and then 'export INSTANCE_HOME=/opt/plone30' to work with
the files in
my plone30 buildout. Not too bad IMO 


------------------------------------------------------------
-------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://
sourceforge.net/services/buy/index.php
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Hanno Schlichting-2 wrote:
> 
> 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 ;)
> 

Ok


Hanno Schlichting-2 wrote:
> 
>> but is there a "zope2-compatible" version
of i18dude that woudl rely 
>> on the same egg versions than the Zope 2.X code
source has ?
> 
> 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.
> 

Well that's because we were thinking about using it within a
package to
automate
some i18n tasks à 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)
 
++
Tarek
-- 
View this message in context: http://www.nabble.c
om/i18ndude-dependencies-and-Zope-2-installs-tf4956504s6748.
html#a14209243
Sent from the Internationalization mailing list archive at
Nabble.com.


------------------------------------------------------------
-------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://
sourceforge.net/services/buy/index.php
_______________________________________________
Plone-i18n mailing list
Plone-i18nlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n