Re: [Zope] stack error with Python 2.1.2
Chris Withers wrote Frank Tegtmeyer wrote: Why does an minor upgrade (called "bug fix" for Python 2.1.1) break an existing application? Smells like some _very_ ugly hacks in Zope or Python.
Nah, just the restricted code in in Zope uses a different compiler than the one in Python leading to badness.
The 2.4.4 and 2.5.0+ restricted python compiler is in synch with the compiler in 2.1.2, the one in Zope 2.4.3 is not.
The problem is more that the Zope code in 2.4.3 and earlier is _broken_. Busted. Incorrect. Wrong. Corrupter of memory, destroyer of data, eater of souls. Python 2.1.1 would silently continue and at some point in the future would crash and burn, maybe. The Zope code includes it's own version of the standard Compiler package. Until 2.4.4 is out, your best hope is to run the 2.4.4 beta. Anthony -- Anthony Baxter <anthony@interlink.com.au> It's never to late to have a happy childhood.
-> > > Smells like some _very_ ugly hacks in Zope or Python. -> -> > Nah, just the restricted code in in Zope uses a different compiler than -> > the one in Python leading to badness. -> -> The problem is more that the Zope code in 2.4.3 and earlier is _broken_. -> Busted. Incorrect. Wrong. Corrupter of memory, destroyer of data, eater of -> souls. Can you be more specific? It seems pretty stable to me, after a couple of months of production usage. Also, I am a bit worried that "version 2.4.3" of anything would corrupt memory, destroy data, and eat souls; so far I have not (to my knowledge) lost any data. I take it you had a bad experience with one of 2.4.3's more serious bugs? :) --Derek
participants (2)
-
Anthony Baxter -
Derek Simkowiak