Second, I am MYSTIFIED (there's no better word) that DC is in such a rush
to REQUIRE the use of Python 2.1 for Zope 2.4, when we're still
waiting for
Py 2.1 final to even come out. Why put all your eggs in that basket, and
why force the community to choose between changing to a bleeding-edge
You may have more than one Python installation on a machine. This in no
way forces you to move "all of your applications" to 2.1. The binary
releases in particular make this drop-dead easy; they come with a bundled
Python, and do not affect any other Python you may have in any way.
right,
On Fri, Apr 13, 2001 at 12:10:52PM -0400, anser wrote:
You may have more than one Python installation on a machine. This in no
way forces you to move "all of your applications" to 2.1. The binary
releases in particular make this drop-dead easy; they come with a bundled
Python, and do not
[anser]
I can't quite help wondering whether someone at DC has maybe gotten so
"into" the development of Py 2.1 that they just can't wait to use its new
stuff, whether it's objectively what's best for Zope or not. The prudent
thing to do would have been to add features as needed using
If what Albert says is true, then Zope 2.4 should REQUIRE Py 2.0 and
SUPPORT Py 2.1, not REQUIRE Py 2.1.
--On Saturday, April 14, 2001 1:14 AM +1000 Albert Langer
[EMAIL PROTECTED] wrote:
The *big* leap is from 1.5.2 to 2.0 which has been out for quite a while.
I18N is *desperately* needed
On Fri, 13 Apr 2001, Tom Neff wrote:
If what Albert says is true, then Zope 2.4 should REQUIRE Py 2.0 and
SUPPORT Py 2.1, not REQUIRE Py 2.1.
But note what he said about "odd numbered releases".
True to form, 2.0 adds a whole load of features, and 2.1 cleans up
after 2.0. ;-)
True,
