Hi Andreas,
I would be really surprised if this were a python problem.
Are you using any other extensions with your product? Can you
post a more complete set of code that shows how this constructor
is really called? It sounds like the heap is getting corrupted
somehow, maybe a bad Py_DECREF?
Hi Andreas,
You might try this: Start Zope in debug mode (./start -D ). Then in your __init__...
class AJFile:
def __init__(self):
import pdb
pdb.set_trace()
self.d = {}
Zope will stop in the debugger. Step through with the debugger and see where things are
going south
On Mon, Dec 25, 2000 at 11:18:23AM -0500, Steve Spicklemire wrote:
>
> Hi Andreas,
>
>You might try this: Start Zope in debug mode (./start -D ). Then in your
>__init__...
>
> class AJFile:
> def __init__(self):
> import pdb
> pdb.set_trace()
> self.d = {}
>
>
> Zope wil
While developing a product I encountered the following fatal
problem. I added a stupid class declaration to my product:
class AJFile:
def __init__(self):
self.d = {}
Inside a function of the product I call "AJF = AJFile()".
Zope/Python call __init__() but crashes before the
initialisati
