John Gordon wrote:
I'm trying to come up with a scheme for organizing exceptions in
my application.
Currently, I'm using a base class which knows how to look up the text
of a specific error in a database table, keyed on the error class name.
The base class looks like this:
class ApplicationExc
On May 8, 4:05 pm, John Gordon wrote:
> I'm trying to come up with a scheme for organizing exceptions in
> my application.
>
> Currently, I'm using a base class which knows how to look up the text
> of a specific error in a database table, keyed on the error class name.
>
> The base class looks li
Am 08.05.2012 22:05, schrieb John Gordon:
[...]
> class QuestionTooShortError(ApplicationException):
> """User entered a security question which is too short."""
> pass
>
> class QuestionTooLongError(ApplicationException):
> """User entered a security question which is too long."""
>
On May 9, 6:05 am, John Gordon wrote:
> I'd like to group the classes underneath a parent class, like so:
>
> class Question(ApplicationException):
>
> class TooShort(ApplicationException):
> pass
>
> class TooLong(ApplicationException):
> pass
>
> This will make it easier
On May 8, 1:05 pm, John Gordon wrote:
> I'm trying to come up with a scheme for organizing exceptions in
> my application.
>
> Currently, I'm using a base class which knows how to look up the text
> of a specific error in a database table, keyed on the error class name.
>
> The base class looks li
On 5/8/2012 4:05 PM, John Gordon wrote:
I'm trying to come up with a scheme for organizing exceptions in
my application.
Currently, I'm using a base class which knows how to look up the text
of a specific error in a database table, keyed on the error class name.
The base class looks like this:
On Tue, May 8, 2012 at 1:05 PM, John Gordon wrote:
> I'm trying to come up with a scheme for organizing exceptions in
> my application.
>
> Currently, I'm using a base class which knows how to look up the text
> of a specific error in a database table, keyed on the error class name.
>
> The base c
In John Gordon writes:
> class QuestionTooShortError(NetIDAppsError):
> """User entered a security question which is too short."""
> pass
> class QuestionTooLongError(NetIDAppsError):
> """User entered a security question which is too long."""
> pass
Oops! These classes inheri
I'm trying to come up with a scheme for organizing exceptions in
my application.
Currently, I'm using a base class which knows how to look up the text
of a specific error in a database table, keyed on the error class name.
The base class looks like this:
class ApplicationException(Exception):
