Actions
Bug #4031
closedset_mem_val() with an invalid value throws the wrong exception
Start date:
09/15/2016
Due date:
% Done:
100%
Estimated time:
0.00 h
Chirp Version:
daily
Model affected:
(All models)
Platform:
All
I read the instructions above:
Description
chirp/settings.py, line 245 is supposed to raise an InvalidValueError
when the value we are trying to set is not in the approved list,
instead a NameError will be raised, because the 'value' variable
used when instantiating the InvalidValueError has not been defined.
The change required is simple, 'value' should be changed to 'mem_val',
I have fixed this in my own version and will submit a patch as soon
as I figure out how to work the hg tools.
Updated by Bernhard Hailer almost 4 years ago
- Status changed from New to Closed
This appears to be complete.
Actions