Make it easier to raise retryable exceptions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zope.publisher |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If I want an exception I raise to cause the request to be retried, I've got two choices:
1. manually wrap it in a Retry exception at the point where I raise it
2. update my publication class's handleException() to covert the exception to a retry (provided retry_allowed=
The first option is useful since it lets the retry behaviour be defined at the point where the exception is raised or defined. However, getOriginalExce
The second option gives us full stack traces, but may not be an option for a general purpose library.
It would be nice if the default ZopePublication
affects: | zope3 → zope.publisher |
Sounds reasonable to me. Is the situation where you need that an
exception that is database related but you don't use ZODB?