Tres Seaver wrote:
> Is there any reason to hide the KeyError behind a 500, rather than
> letting it propagate to the application? In this implementation, we
> lose the information about the bad 'status' value.
I agree, but I hit a legacy design snag. The handleException() method
still calls s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shane Hathaway wrote:
> Log message for revision 95601:
> Fixed LP #322486: setStatus() now allows any int()-able status value.
Yay!
> Modified: zope.publisher/trunk/src/zope/publisher/http.py
> ===
