-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Diez B. Roggisch wrote:
> On Tuesday 15 December 2009 17:55:58 Malthe Borch wrote:
>> 2009/12/15 Diez B. Roggisch <diez.roggi...@ableton.com>:
>>> I guess the question has been asked before, and I'm aware that the state
>>> of python 2.5 support is ultimately a zope-issue.
>> Python 2.5 is supported since two years. We commonly use Python 2.6 though.
> 
> Hm, I might have confused something then. But it says so on the Zope 2.11.4 
> release page:
> 
>   http://www.zope.org/Products/Zope/2.11.4/Zope-2-11-4-released
> 
> that
> 
> """
> Zope 2.11 requires Python 2.4.5 (Python 2.4.4 is still acceptable). Older 
> Python versions are no longer supported. Python 2.5 is not supported at this 
> time.
> """

Zope 2.11 is now the "old stable" version:  it won't ever be *supported*
on Pythonn 2.x where x >= 4.  It may still *run* on a later Pyhont, however.

> And building zopelib with python2.5 lead to segfaults on my machine, and in 
> the installation instructions on 
> 
>  http://repoze.org/quickstart.html
> 
> it says explicitly
> 
> """
> Please note that none of repoze.plone, repoze.zope2 or repoze.grok work 
> properly under Python 2.5. These packages require Python 2.4.
> """

zopelib was a way to get egg-based deployment of Zope prior to the fully
egg-based 2.12.  You need either to upgrade to use Zope 2.12 (and drop
zopelib), or else stay on Python 2.4.



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksnyI4ACgkQ+gerLs4ltQ42aQCfWUD8cuq795K+Dvv0ZzjYohnd
jkgAni7jhJIiQ9xhHXqd0L0WbPH07mp+
=9vgC
-----END PGP SIGNATURE-----
_______________________________________________
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Reply via email to