When a detector has a serious problem (e.g. I/O Error, division by zero,
etc,) ultimately a DetectorError is raised. This is defined in
cgi/exceptions.py.

Now I got a Detector Error without any message about what was wrong.

Looks like the Detector Error *does* print its parameters with python3
but not with python2, see the test-script below.

Anybody in-the-know can tell us how to correctly define a custom
exception in python2 that prints its parameters?

python3:

>>> from roundup.cgi.exceptions import DetectorError
>>> raise DetectorError ('Bla', 'some html', 'some text')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
roundup.cgi.exceptions.DetectorError: ('Bla', 'some html', 'some text')

python2:
>>> from roundup.cgi.exceptions import DetectorError
>>> raise DetectorError ('Bla', 'some html', 'some text')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
roundup.cgi.exceptions.DetectorError

I'm now calling the base class __init__ with a message manufactured from
some of the parameters.

Ralf, I see you committed a change to fix this.
Was it a successful fix so this can be closed?

On Tue, Sep 17, 2019 at 09:04:34PM +0000, John Rouillard wrote:
> 
> Ralf, I see you committed a change to fix this.
> Was it a successful fix so this can be closed?

Yes, I think we can close it although I've not yet observed the effect
of the change in a running system yet. (I *did* test it on the
command-line as indicated).

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com

Closing as fixed.