Hi,
Shane Hathaway wrote:
I'm working on enhancing zope.app.apidoc, but I ran into an exception
that's hard to decipher. I've attached the traceback. I don't know
which __init__() it's complaining about, and I don't know how to find
out. What can I do to find out which __init__() the
Christian Theune wrote:
Shane Hathaway wrote:
I'm working on enhancing zope.app.apidoc, but I ran into an exception
that's hard to decipher. I've attached the traceback. I don't know
which __init__() it's complaining about, and I don't know how to find
out. What can I do to find out which
Shane Hathaway wrote:
Christian Theune wrote:
Shane Hathaway wrote:
I'm working on enhancing zope.app.apidoc, but I ran into an exception
that's hard to decipher. I've attached the traceback. I don't know
which __init__() it's complaining about, and I don't know how to find
out. What
Christian Theune wrote:
Shane Hathaway wrote:
Unfortunately, the adapter hook is in C. It would be great if I could
switch it to Python. Is that possible?
I remember being able to step into it. pdb then put me into the next
Python-level within there ...
Probably you can delete some
Hello Shane,
SH For me, the value is in the comfort of a transparent database. I want
SH to know exactly what Zope is storing. FileStorage makes that fairly hard.
There is half-baked solution at z3c.zodbbrowser.
Without knowing your exact requirements, I suggest you take a look.
--
Best
I'm working on enhancing zope.app.apidoc, but I ran into an exception
that's hard to decipher. I've attached the traceback. I don't know
which __init__() it's complaining about, and I don't know how to find
out. What can I do to find out which __init__() the adapter hook is
trying to call?
