Mercurial > p > roundup > code
view roundup/exceptions.py @ 7738:ce0c40b6cdc3
doc: replace URL action example with form
The example to provide a link to take or resolve an item was broken.
Roundup has required a POST not GET for changes to the database for
a while. This example was never fixed.
Replaced a link using GET with a POSTed form. This changes the
activating element from a link to a button. The button could be
restyled as a link using CSS I think.
The original example was also not canonical. It used :action rather
than the canonical @action.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Tue, 13 Feb 2024 19:45:44 -0500 |
| parents | 273c8c2b5042 |
| children | e882a5d52ae5 |
line wrap: on
line source
"""Exceptions for use across all Roundup components. """ __docformat__ = 'restructuredtext' class RoundupException(Exception): pass class LoginError(RoundupException): pass class RateLimitExceeded(Exception): pass class Unauthorised(RoundupException): pass class RejectBase(RoundupException): pass class Reject(RejectBase): """An auditor may raise this exception when the current create or set operation should be stopped. It is up to the specific interface invoking the create or set to handle this exception sanely. For example: - mailgw will trap and ignore Reject for file attachments and messages - cgi will trap and present the exception in a nice format """ pass class RejectRaw(Reject): """ Performs the same function as Reject, except HTML in the message is not escaped when displayed to the user. """ pass class UsageError(ValueError): pass # vim: set filetype=python ts=4 sw=4 et si
