id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 12385,Trap NotImplementedError,Ryan J Ollos,Ryan J Ollos,"Raising a `NotImplementedError` exception results in the following page: [[Image(Screen Shot 2016-03-04 at 22.41.55.png)]] Note that this standard error screen suggests that the user might //create a ticket//. If the developer is explicitly raising a `NotImpementedError`, we probably don't want users reporting these issues (#11611). Ideally the `NotImplementedError` would have an explanation, perhaps even a link to the ticket in which the feature/method will be implemented. That may be applicable to the scenario that led to the screen capture. {{{#!python Traceback (most recent call last): File ""/usr/local/virtualenv/1.0-stable/lib/python2.7/site-packages/trac/web/main.py"", line 554, in _dispatch_request dispatcher.dispatch(req) File ""/usr/local/virtualenv/1.0-stable/lib/python2.7/site-packages/trac/web/main.py"", line 247, in dispatch resp = chosen_handler.process_request(req) File ""/usr/local/virtualenv/1.0-stable/lib/python2.7/site-packages/trac/versioncontrol/web_ui/log.py"", line 271, in process_request for cpath, kind, chg, bpath, brev in changeset.get_changes(): File ""/usr/local/virtualenv/1.0-stable/lib/python2.7/site-packages/trac/versioncontrol/api.py"", line 1244, in get_changes raise NotImplementedError NotImplementedError: }}} We could add a `TracNotImplementedError`: {{{#!python class TracNotImplementedError(TracError, NotImplementedError): }}} Or we could trap `NotImplementedError` where `TracError` is trapped.",defect,closed,normal,1.0.11,general,,normal,fixed,exception,,,`NotImplementedError` is trapped and a system message is presented to the user rather than the error reporting page.,,