Does zope still need a python compiled with "--without-pymalloc" ?
Hi, well, the subject says it all. Why was it needed at all? I still compile my python --without-pymalloc from the pre-python-2.1.3 days when zope suffered from bugs in python. I nowadays use Zope-2.5.1 and python 2.1.3, mostly. Thanks, /dario - -------------------------------------------------------------------- Dario Lopez-Kästen, dario@ita.chalmers.se IT Systems & Services System Developer/System Administrator Chalmers University of Tech.
Dario Lopez-Kästen wrote at 2003-2-5 11:50 +0100:
well, the subject says it all. Why was it needed at all?
I still compile my python --without-pymalloc from the pre-python-2.1.3 days when zope suffered from bugs in python.
I nowadays use Zope-2.5.1 and python 2.1.3, mostly. I am almost sure, you no longer need it.
At least, we use Python 2.1.3 compiled without this option and do not see problems (attributable "malloc"). Dieter
Dieter Maurer wrote I am almost sure, you no longer need it. At least, we use Python 2.1.3 compiled without this option and do not see problems (attributable "malloc").
The (known) bugs that pymalloc (and cycle-gc) triggered are fixed in 2.1.3. Anthony -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.
Great, thanks to both of Dieter and Anthony! Sincerely, /dario ----- Original Message ----- From: "Anthony Baxter" <anthony@interlink.com.au>
Dieter Maurer wrote I am almost sure, you no longer need it. At least, we use Python 2.1.3 compiled without this option and do not see problems (attributable "malloc").
The (known) bugs that pymalloc (and cycle-gc) triggered are fixed in 2.1.3.
Anthony
participants (3)
-
Anthony Baxter -
Dario Lopez-Kästen -
Dieter Maurer