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

[Chris McDonough]

On Thu, 2003-11-27 at 01:03, Tim Peters wrote:
> 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>).

Yes, sorry, I meant "tested" as in presumably actually run by a wide
variety of end users (2.7b3 is the first 2.7 release for which Python
2.3.2 is required... all of its other betas required 2.2.3).

> 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.

FWIW, I am not at all concerned about the stability of Python 2.3.2, I
know it's a very solid release  and I don't need any convincing.  I was
concerned about using the combination of Zope 2.7 with Python 2.3.2 in
production, given the relatively short time period in which the
combination has actually been used by normal people. ;-)  The fact that
ZC is beginning to use the combination in production pretty much negates
that concern for me, though, and probably for other folks as well.

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

Great.  I presume that the auditing effort is centered pretty much
purely around security, then.  If I find some time, I may try to
identify some other things that need auditing (and actually do the work,
or at least start it).

- C