Andreas Jung wrote:
> On 27.10.2008 18:55 Uhr, Sidnei da Silva wrote:
>> On Mon, Oct 27, 2008 at 3:42 PM, Andreas Jung<[EMAIL PROTECTED]> wrote:
>>> Why do we need these backports on the current maintenance branches?
>> They are small cleanups that could potentially allow someone to run
>> Python 2.5 or 2.6 if they really really really wanted to, but note
>> should be made that it would be completely and utterly unsupported.
> Please create branches first and then lets review the changes. What is
> the state of the compatability of Z3 modules with Python 2.5/2.6 as used
> in Zope 2.10/2.11?
Zope 2.10 contains Zope 3.3 which most likely doesn't work on Python
2.5. Nobody has bothered to take a look, really, since it's ages old.
Zope 2.11 contains the Zope 3.4 KGS, as far as I'm aware. If the 3.4 KGS
refers to the latest bugfix releases of all packages, then it works on
Superficially, many Zope 3 packages also work on Python 2.6 (e.g. Grok
runs), but a closer look reveals various test failures.
IMHO we shouldn't worry about 2.10 and 2.11 and just care about 2.12 at
this point. By now it should work with Python 2.5, right? Let's release
it soonish. Not only will it bring Python 2.5 compatibility but it also
gets rid of Acquisition-wrapped views and introduces (optional)
__parent__ pointers. Three years after having started the
implementation, I think it's time to get it out there :)
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -