[Zope-Coders] Linux Test Results - HEAD/Py2.2 - Not OK :-(

[Tim Peters]

[Chris McDonough]
> Sure, I understand this.  It's just tempting to attempt to bridge the
> (currently very small) gap, as 9 of the 11 months of 2.7 development
> and betas have presumably been tested using 2.2 only.

The various Zope and Zope3 test suites were run under Python 2.3 CVS during
2.3 development all along, including the full set of hairy and
time-consuming ZEO and ZRS tests.

    http://www.zopenewbies.net/

started running 2.3 final the day after it was released, and is currently
running Zope 2.7b3 + Python 2.3.2 (they seem much better at keeping up to
date than non-newbies <wink>).

> ...
> I'd pretty much agree, given the information that ZC is now running
> 2.7 in production using Python 2.3.  I didn't know this at all.  Like
> you, I'm not eager to put much stock in the testimony of developers
> running Zope 2.7/Py 2.3 on their personal systems, and I'd rather
> rely on what I know works (or believe works, anyway due to some long
> period of code exposure to the wider world ;-) rather than the
> promises of said developers, at least for "high risk" production work.

Well, that's as much reason to fear Zope 2.7 as Python 2.3.2.  Keep in mind
that thousands of applications use Python -- Zope is just one of
them, and many Python users have switched to 2.3 in the 4 months since it
was first released.  It's universally judged to be faster and stabler than
2.2, both of which have spurred quick adoption elsewhere.  Even the
conservative-by-design Python Business Forum recommends 2.3.2 to anyone who
asks.  BTW, the only critical bug reports we've gotten against 2.3 so far
turned out to have been bugs in 2.2 too; the difference is that they're
already fixed in 2.3 CVS, and may never get fixed in a 2.2 release.

> I'll note that the community at large really doesn't know any what the
> current status of 2.7 production auditing/testing is.  It might be
> helpful for those involved with this at ZC to be a bit more inclusive
> with respect to the results, if not the actual work.  I would try to
> participate in a bugday or two with this as the topic, for instance,
> and I'd love to know what work has been done towards this.

Substantial work has gone, and is going, in to a security audit of Zope 2.7
and Python 2.3.2.  I don't want to comment on sensitive work in progess, but
I'll note that no problems unique to Python 2.3.2 had been uncovered last I
heard (which was last week).