[Zope-Coders] RE: [Zope-Checkins] CVS: Zope/doc - INSTALL.txt:1.32

[Brian Lloyd]

> Jup, that is the reason. The HEAD currently does not work with Python
> 2.2 except Shane's branch I think. So we can not proclaim the usage
> of Python 2.2 and (at least) I recommend 2.1.3.
>
> Andreas
>
> > I think the big *if* relates to "do you still need Makefile.pre.in?"  If
> > the answer is 'no' then there is no reason 2.2 could not be endorsed.
> >
> > --
> > Matt Kromer

(FYI - moving this to zope-coders. :)

It's actually more than any particular issue like Makefile.pre.in.
It's a question of resources. I'm not willing to make Python 2.2
the "official" platform for 2.6 until we've done the requisite
homework, and right now there is no one available to do it.

Does that mean it _won't_ work on 2.2? No. It just means that if
you do it, you do it at your own risk for now, because no one
has specifically gone through to carefully assess the 2.1->2.2
changes for any effects on Zope. We spent quite some time doing
this for the move to 2.1:

http://dev.zope.org/Wikis/DevSite/Projects/SupportPython21/

While there are probably fewer changes from 2.1 -> 2.2, we still
need to assess their impacts before making 2.2 the officially
platform. In particular, I'd be surprised if new-style classes,
descriptors, etc. didn't have some sort of impact (I _know_
we use explicit type() checks in places where we probably
wouldn't want to in 2.2).

Another issue is making sure that none of the new features in
2.2 have a side effect of opening a trap door in the Zope 2
security model - or a side effect of breaking things that people
might expect to work. Will the Zope 2 security policy let you
use an iterator? Can you write generators in Python Script objects?
etc.

Whatever the answers are, we need to find them out, write
them down and do all of the other due diligence before we
change the officially supported platform.



Brian Lloyd        brian@zope.com
V.P. Engineering   540.361.1716
Zope Corporation   http://www.zope.com