Mercurial > p > roundup > code
view roundup/exceptions.py @ 6428:32a04dc87b30
Make HTMLClass::history signature compatible to _HTMLItem::history
_HTMLItem::history accepts 4 optional named parameters. If a template
(e.g. issue.item.html) calls history with a named param and then is
called in the context of creating a new issue, you get a traceback.
Change HTMLClass::history to accept any named parameter so
adding new named params to _HTMLItem::history doesn't
require a change to HTMLClass::history.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Fri, 04 Jun 2021 07:28:18 -0400 |
| parents | c177e7128dc9 |
| children | e16b7d47fdb2 |
line wrap: on
line source
"""Exceptions for use across all Roundup components. """ __docformat__ = 'restructuredtext' class RoundupException(Exception): pass class LoginError(RoundupException): 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
