Mercurial > p > roundup > code
view roundup/exceptions.py @ 5748:943e61bc26d5
Fix issue2551029 (Jinja2 template install error) by deleting
config.ini from all templates. Looks like classic and minimal never
included a config.ini. Presence of config.ini stopped
'roundup-admin install' from generating an up to date config.ini.
Created special option class for backend database. Comment now uses
roundup.backend.list_backends to give user indication of valid values.
Also we now get an error if user specifies invalid backend.
Moved backend setting to top or [rdbms] section. It is the most
important thing in there and if set to anydbm (or some other non-rdbm)
the rest of the settings can be ignored.
Change rdbms config section comment to indicate that the backend
setting was used by other database backends. (e.g. if set to anydbm).
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 01 Jun 2019 09:05:23 -0400 |
| parents | 32f95ec6bd8e |
| children | 292c9dfd06bd |
line wrap: on
line source
"""Exceptions for use across all Roundup components. """ __docformat__ = 'restructuredtext' class LoginError(BaseException): pass class Unauthorised(BaseException): pass class Reject(BaseException): """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
