On Tue, Sep 14, 2010 at 12:00:58PM +0200, Marius Gedminas wrote:
> What are the most obscure error conditions you've encountered while
> developing Zopeish[1] applications?
Trying to add a proxied object to the database gives an error that
more or less clearly states this condition (proxies are un
On Tue, Sep 14, 2010 at 12:00, Marius Gedminas wrote:
> What are the most obscure error conditions you've encountered while
> developing Zopeish[1] applications?
>
> [1] ZTK, Grok, Bluebream, the old Zope 3.x KGSes all qualify.
>
> I'm talking about situations where the error message/traceback ar
> From: Marius Gedminas
> Date: Tue, Sep 14, 2010 at 11:00 AM
> Subject: [Zope-dev] Survey: most obscure errors
> To: zope-dev@zope.org
>
>
> What are the most obscure error conditions you've encountered while
> developing Zopeish[1] applications?
>
> [1] ZTK
Hi
It doesn't happen to me any longer, cause I learned my lesson,
but in the beginning I was always confused about the error message
when an exception happened in the __init__ method of a view.
The Exception gets caught, and interpreted as if the object object/view
does not exist. I then always c
What are the most obscure error conditions you've encountered while
developing Zopeish[1] applications?
[1] ZTK, Grok, Bluebream, the old Zope 3.x KGSes all qualify.
I'm talking about situations where the error message/traceback are
disconnected from the actual cause. For example, forgetting t
