view roundup/exceptions.py @ 7697:c73a1177c2b2

fix: roundup-demo, interactive mode would nuke an existing tracker. Tonu Mikk demonstrated a bug in roundup-demo. When invoked without a tracker home on the command line, it would nuke an existing directory specified interactively. There is still a minor bug. If an invalid home directory is specified, roundup-demo will prompt for the template to use before reporting: Error: Refusing to nuke non-tracker directory: but this doesn't cause data loss so not worth fixing at this time.
author John Rouillard <rouilj@ieee.org>
date Wed, 08 Nov 2023 21:18:34 -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

Roundup Issue Tracker: http://roundup-tracker.org/