Re: [Zope-dev] [BUG] Python 2.1.2 & Zope 2.4.1
This has been explained recently (--> mailing list archives, probably through Google search for "f_stacksize").
I did, without a great success.
Summary, you need to upgrade Zope, too!
If only I could... You can't make your customer migrate their Zope version in 2hours. Our servers are hosting dozens of website for dozens of customer. Moving to a newer Zope is not just a matter of installing a new version... For example, we have a CMF site that will only work with Zope 2.4.1. We tried to migrate to CMF 1.2 or Zope 2.4.3, without success (crashes, security machinery misteries, etc.). CMF is still too dark to manipulate it as we would wish.
Viele Grüße Dieter
Olivier Deckmyn writes:
This has been explained recently (--> mailing list archives, probably through Google search for "f_stacksize").
I did, without a great success.
Summary, you need to upgrade Zope, too!
If only I could... Zope 2.4.3 will not work with Python 2.1.2.
Unfortunately, you either upgrade Zope or downgrade Python... A partial upgrade may be possible, though. See the mailing list archives. Dieter
Dieter Maurer wrote:
Zope 2.4.3 will not work with Python 2.1.2.
This is not literally true. Zope 2.4.3 will work fine with Python 2.1.2. However, Python 2.1.2 doesn't ignore stacksize computation problems like Python 2.1.1. Instead of silently corrutping memory and continuing like 2.1.1, Python 2.1.2 will stop with an assertion error. This means that Zope 2.4.3 won't really run under 2.1.2 for very long if you've got a codepath that tickles a "compiler package" bug, but at least it won't fail mysteriously with odd symptoms. Zope 2.4.3 will run for *longer* under Python 2.1.1, but it will fail with other more mysterious symptoms. Hopefully, this will clear some of the confusion up. For maximum stability if you're running some 2.4.X-series Zope under Python 2.1.X: - Upgrade your Zope to 2.4.4 (wait for final if you don't like the current "beta" status of 2.4.4) - Upgrade your Python to 2.1.2 Do these two steps *at the same time*. You should have increased stability and availability after that. - C
participants (3)
-
Chris McDonough -
Dieter Maurer -
Olivier Deckmyn