Jon Emmons wrote at 2007-5-31 11:06 -0400:
> ...
>I still don't know why python errors will just quietly cause things to fail
>with no zope error at all. Nothing... That may be something I just have to
>live with. Very difficult to debug and develop with though.
This is a *very* unusual behavio
The example 'var1 = var2' should cause the NameError exception.
"NameError: name 'var2' is not defined"
You might want to check your 'error log' objects for the error messages. If
you don't have an error log object, it might be a good idea to create one.
On 5/31/07, Maciej Wisniowski <[EMAIL
> Var1 = var2
>
> Where var2 is undefined (i.e. has never been assigned anything)
>
> Just silent failure. No error.
So how do you know there is a failure then?
There is really nothing in event.log and nothing in error_log?
--
Maciej Wisniowski
___
Z
PROTECTED]
Sent: Thursday, May 31, 2007 11:15 AM
To: Jon Emmons; zope@zope.org
Subject: Re: [Zope] Uncaptured python exception
- Original Message -
From: "Jon Emmons" <[EMAIL PROTECTED]>
To: "'Andreas Jung'" <[EMAIL PROTECTED]>; "'Jonathan'
- Original Message -
From: "Jon Emmons" <[EMAIL PROTECTED]>
To: "'Andreas Jung'" <[EMAIL PROTECTED]>; "'Jonathan'" <[EMAIL PROTECTED]>;
Sent: Thursday, May 31, 2007 11:06 AM
Subject: RE: [Zope] Uncaptured python exce
--On 31. Mai 2007 11:06:17 -0400 Jon Emmons <[EMAIL PROTECTED]>
wrote:
Thanks all for your help.
I guess I was worried about nothing. Previous versions of zope did not
generate those messages.
Nonsense. Such error messages are shown by Zope since ages.
I thought it was why I was getti
0:25 AM
To: Jon Emmons; 'Jonathan'; zope@zope.org
Subject: RE: [Zope] Uncaptured python exception
--On 31. Mai 2007 10:12:35 -0400 Jon Emmons <[EMAIL PROTECTED]>
wrote:
> Oops, my bad.
>
> Python is 2.4.4. (not 3.4) perhaps my python needs to be moved back a
> bit.
--On 31. Mai 2007 10:12:35 -0400 Jon Emmons <[EMAIL PROTECTED]>
wrote:
Oops, my bad.
Python is 2.4.4. (not 3.4) perhaps my python needs to be moved back a
bit.
I don't get any error in the error log from the zope admin, just this
cryptic msg from the window that zope is running in.
2007-
On 5/31/07, Jon Emmons <[EMAIL PROTECTED]> wrote:
I don't get any error in the error log from the zope admin, just this
cryptic msg from the window that zope is running in.
2007-05-31 09:48:49 ERROR ZServer uncaptured python exception, closing
channel (socket.error:(104, 'Connection reset
by pe
ROTECTED]
Sent: Thursday, May 31, 2007 10:07 AM
To: Jon Emmons; zope@zope.org
Subject: Re: [Zope] Uncaptured python exception
- Original Message -
From: "Jon Emmons" <[EMAIL PROTECTED]>
To:
Sent: Thursday, May 31, 2007 9:58 AM
Subject: [Zope] Uncaptured python exception
&
- Original Message -
From: "Jon Emmons" <[EMAIL PROTECTED]>
To:
Sent: Thursday, May 31, 2007 9:58 AM
Subject: [Zope] Uncaptured python exception
I am using zope 2.9, python 3.4. when I have a bug in my python I get
"Uncaptured Python Exception" coming from zope.
This is a nightmar
--On 31. Mai 2007 09:58:43 -0400 Jon Emmons <[EMAIL PROTECTED]>
wrote:
I am using zope 2.9, python 3.4.
Python 2.4 you mean...
when I have a bug in my python I get
"Uncaptured Python Exception" coming from zope.
Without the full traceback such a question is pretty much worthless.
Uncap
12 matches
Mail list logo
