Mercurial > p > roundup > code
view roundup/exceptions.py @ 7687:4dda4a9dfe0b
doc: add comment on method to set savepoint_limit dynamically
savepoint_limit isn't a real config option as in config.ini. I
generate one on the fly for use in the backend during import.
While this is arguably a valid config option, it is also something
that is niche (import a tracker to postgres) and adds clutter to
config.ini.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 29 Oct 2023 13:18:36 -0400 |
| 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
