python versions and zope
PEP 6: "In general, only the N-1 release will be under active maintenance at any time." Python 2.3 is scheduled for early July (PEP 283i and dev-pyBthon mailings). Here's a tentative release schedule that follows the above guidelines: alpha 1 -- December 31, 2002 alpha 2 -- February 19, 2003 beta 1 -- April 25, 2003 beta 2 -- late May rc 1 -- late June final -- early July Unless I am mistaken, Zope 2.5.1, 2.6.0, 2.6.1 all *require* Python 2.1.3 and will not work with Python 2.2 and later. Do we have a problem?
Dennis Allison wrote at 2003-6-25 09:31 -0700:
PEP 6: "In general, only the N-1 release will be under active maintenance at any time."
Python 2.3 is scheduled for early July (PEP 283i and dev-pyBthon mailings).
Here's a tentative release schedule that follows the above guidelines:
alpha 1 -- December 31, 2002 alpha 2 -- February 19, 2003 beta 1 -- April 25, 2003 beta 2 -- late May rc 1 -- late June final -- early July
Unless I am mistaken, Zope 2.5.1, 2.6.0, 2.6.1 all *require* Python 2.1.3 and will not work with Python 2.2 and later.
Do we have a problem?
No, because * Python 2.1.3 runs very reliably. We do not need maintenance for it. * Zope 2.6 does run with Python 2.x (for "x >= 2") Dieter
On Thursday 26 June 2003 04:18 pm, Dieter Maurer wrote:
Dennis Allison wrote at 2003-6-25 09:31 -0700:
Unless I am mistaken, Zope 2.5.1, 2.6.0, 2.6.1 all *require* Python 2.1.3 and will not work with Python 2.2 and later.
Do we have a problem?
No, because
* Python 2.1.3 runs very reliably. We do not need maintenance for it.
* Zope 2.6 does run with Python 2.x (for "x >= 2")
Really? Is that official? Because actually, there's a lot of 3rd party modules that require 2.2+ (the first that comes to mind is the "constraints" module), that I would like to start using. So being forced to stick with 2.1 has been a bit annoying (have to maintain two versions of Python, can't integrate some packages with Zope, etc). If it works, thanks for the info. I'll definitely try it out. I assume it's a no-brainer that Zope3 will work with later Python versions, of course. Cheers, Terry -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi Spaceworks http://www.anansispaceworks.com
Unless I am mistaken, Zope 2.5.1, 2.6.0, 2.6.1 all *require* Python 2.1.3 and will not work with Python 2.2 and later.
Do we have a problem?
No, because
* Python 2.1.3 runs very reliably. We do not need maintenance for it.
* Zope 2.6 does run with Python 2.x (for "x >= 2")
Really? Is that official? Because actually, there's a lot of 3rd party modules that require 2.2+ (the first that comes to mind is the "constraints" module), that I would like to start using. So being forced to stick with 2.1 has been a bit annoying (have to maintain two versions of Python, can't integrate some packages with Zope, etc).
If it works, thanks for the info. I'll definitely try it out.
I assume it's a no-brainer that Zope3 will work with later Python versions, of course.
There's an opinion from one person (from russian zopylist) who had big practice in connecting Zope & Python222: The workability of Zope & Python222 is finished when you try to inherit from object & extension class at once, as well as other analog innovations; they're conflicting with ExtensionClass. If he's reading the list he would probably explain it in more details.. WBR, Serge
On Thu, Jun 26, 2003 at 08:36:36PM -0700, Terry Hancock wrote:
On Thursday 26 June 2003 04:18 pm, Dieter Maurer wrote:
Dennis Allison wrote at 2003-6-25 09:31 -0700:
Unless I am mistaken, Zope 2.5.1, 2.6.0, 2.6.1 all *require* Python 2.1.3 and will not work with Python 2.2 and later.
Do we have a problem?
No, because
* Python 2.1.3 runs very reliably. We do not need maintenance for it.
* Zope 2.6 does run with Python 2.x (for "x >= 2")
Really? Is that official? Because actually, there's a lot of 3rd party modules that require 2.2+ (the first that comes to mind is the "constraints" module), that I would like to start using. So being forced to stick with 2.1 has been a bit annoying (have to maintain two versions of Python, can't integrate some packages with Zope, etc).
If it works, thanks for the info. I'll definitely try it out.
ONe other snag: python >= 2.2 adds docstrings to many built-in types that did not previously have them. This exposes a lot of new stuff via the web which could be a security risk. IIRC this is addressed in the 2.6 CVS branch, but it's not in the released 2.6.0 or 2.6.1.
I assume it's a no-brainer that Zope3 will work with later Python versions, of course.
currently zope x3 requires python >= 2.2.3. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's ALMIGHTY HAMMERLIKE ROBOT INDUSTRIALIST! (random hero from isometric.spaceninja.com)
Terry Hancock wrote at 2003-6-26 20:36 -0700:
On Thursday 26 June 2003 04:18 pm, Dieter Maurer wrote:
Dennis Allison wrote at 2003-6-25 09:31 -0700:
Unless I am mistaken, Zope 2.5.1, 2.6.0, 2.6.1 all *require* Python 2.1.3 and will not work with Python 2.2 and later.
Do we have a problem?
No, because
* Python 2.1.3 runs very reliably. We do not need maintenance for it.
* Zope 2.6 does run with Python 2.x (for "x >= 2")
Really?
Really.
Is that official?
No, but a message in the mailing list told that the warning for Python 2.2 usage has been removed (search the archives). What difference makes it whether it is official or not? There is a known issue with Zope and Python 2.2 usage: In Python 2.2, elementary data types have docstrings. As a consequence, some attributes of Zope objects (e.g. "manage_options") may be read by direct Web access. Some think this were a security concern. Dieter
participants (5)
-
"Sergey Badamshin -
Dennis Allison -
Dieter Maurer -
Paul Winkler -
Terry Hancock