> Please, please, please, don't propagate dodgy and incorrect fixes like
> the above (removing the assertion). The assertion is in the code for a
> very, very good reason.
I obviously know this !! But couldn't find another way to have my servers
restart this sunday.
I just regret that this probl
>>> "Olivier Deckmyn" wrote
> assertion "STACK_LEVEL() <= f->f_stacksize" failed: file "Python/ceval.c",
> line 687
This is a new assertion, put in to catch the case where the RestrictedCompiler
code used by PythonScripts incorrectly calculates stack size.
> After some hours of researches, I hav
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.
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 Pyt
On Mon, Jan 28, 2002 at 10:32:11AM -0500, Paul Everitt wrote:
> All in all, only a few days separate the two releases, and obviously CVS
> people have been able to get at changes all along. Thus, I don't think
> this is an extreme case.
Also note that downloading a source release from CVS is v
Leonardo Rochael Almeida wrote:
> I'm really disappointed with ZC for putting out a new release of Zope
> instead of a fixed version of the release most everyone is currently
> using.
2.4.4 is ready, but there's a problem with the Windows build. I suppose
we could just put the others up there
> BTW, Chris, what Olivier saw couldn't automatically lead him to
> correlate with the other Zope crashes, since the other reports don't
> mention the 'assertion' error message he saw, which he concluded was the
> cause of his problems.
http://zope.nipltd.com/public/lists/zope-archive.nsf/47ba74c
> 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
What you just 'fixed' is an assertion against a memory corruption bug in
all Zope versions between 2.4.0 and 2.4.3, inclusive. Zope version 2.4.4
(which hasn't been released, Hey ZC! wake up! stabilizing 2.4 is more
important than releasing 2.5 in my book! Now that you've done the latter
can you c
ROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, January 27, 2002 11:45 AM
Subject: [Zope-dev] [BUG] Python 2.1.2 & Zope 2.4.1
> Hi,
>
> I decided to upgrade my Python 2.1.1 to Python 2.1.2 (in order to gently
> move to 2.5 later).
>
> My Zope instances were working quite fine
Hi,
I decided to upgrade my Python 2.1.1 to Python 2.1.2 (in order to gently
move to 2.5 later).
My Zope instances were working quite finebut...randomly I got a core
dump (!) and the following message in logs :
assertion "STACK_LEVEL() <= f->f_stacksize" failed: file "Python/ceval.c",
line
11 matches
Mail list logo
