From 9f6d6462a9cef37735a9d4c61921d04934fd9864 Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Wed, 11 Nov 2015 03:22:38 +0000 Subject: Configure pylint to use the pylint-django plugin, which (mostly) understands Django's exotic metaclasses, which in turn allows us to re-enable a number of pylint checks we had disabled. While we were at this, stripped out a bunch of old pylint pragmas, then added back the subset that were really needed. As usual with pylint, this turned up a few real bugs along with an awful lot of noise. svn path=/branches/tk705/; revision=6162 --- rpki/exceptions.py | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'rpki/exceptions.py') diff --git a/rpki/exceptions.py b/rpki/exceptions.py index cbdb9f83..d66ad00c 100644 --- a/rpki/exceptions.py +++ b/rpki/exceptions.py @@ -241,3 +241,9 @@ class UnexpectedUpDownResponse(RPKI_Exception): class BadContentType(RPKI_Exception): "Bad HTTP Content-Type." + +class ResourceClassMismatch(RPKI_Exception): + "Up-down resource class does not match." + +class IRDBExpired(RPKI_Exception): + "Back-end database record has expired." -- cgit v1.2.3