On Tue, 16 Jul 2002, Ross Boylan wrote:
The Zope Developer's Guide and the API docs (Zope 2.5) present
different stories about how to add things to object managers. I don't
really follow what the API stuff is doing. This is a request for
clarification.
Devguide says do
def
Working on the Zope 2.7 branch I noticed a very strange crash while
running the test suite. I re-checked out the Zope 2 cvs head, rebuilt
everything from scratch and I still get the crash. I'm about out of
ideas so I thought I'd post what I know here in case anyone else can
confirm or give
The gvibDA interbase adapter really must have exactly one database connection
shared among all threads.
Even though the DA is derived from THUNKED_TM, there are still multiple instances of
the DA created, one for each thread (depending on server load).
What I really want is one DA that is
jeffrey wrote:
Jens Vagelpohl writes:
have you read about the python crash-bug stemming from tiny thread
stack sizes on freebsd and applied the patch? the mailing list
archives should tell you what to do.
Ahh, thanks! I think I found the right patch and all. Won't get to find
Barry A. Warsaw wrote:
Working on the Zope 2.7 branch I noticed a very strange crash while
running the test suite. I re-checked out the Zope 2 cvs head, rebuilt
everything from scratch and I still get the crash. I'm about out of
ideas so I thought I'd post what I know here in case anyone else
I've just committed the change to the file that dictates checkin notice
routing so that Zope3 checkins are directed to the [EMAIL PROTECTED]
mailling list, instead of being included in the [EMAIL PROTECTED]
list. For those of you on the latter list interested in continuing to get
zope3
I have a product with a number of classes that have subclasses. It
seems natural to make the screens for the subclasses by extending
those of the superclass. Can anyone suggest a good way to do that?
The naive approach is that I have a manage_edit_A.dtml that gives a
management screen for A.
MTK == Matthew T Kromer [EMAIL PROTECTED] writes:
MTK On *my* RedHat 7.3 system, I cannot reproduce your problem.
MTK However, you do note that exception 0x6e727574 is ASCII for
MTK 'nrut' or 'turn' backwards. I dont know if that's meaningful
MTK or not. I usally watch out
