Tres Seaver wrote:
Exactly. The point is that the "adverse effect" *already happened*, in
some prior request, probably due to one of Chris' beloved hasattrs ;).
The current request should *not* be prevented from continuing.
Why not?
Chris, take this as a fiat: this one will *never* turn into an exception.
It's already an exception, you and Florent seem intent on burying that
fact. Can you give me some specific examples in the past of where this
has been of benefit?
Every single time I've encountered this, the fact that the exception is
caught has been a total hinderance :-(
That said, I'm also aware that there are currently 4 of us talking about
this, 2 on each side. What does the rest of the community think?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
