Merge lp:~oem-qa/checkbox/patch_apport_interface_yesno into lp:checkbox
Proposed by
Javier Collado
Status: | Merged |
---|---|
Merged at revision: | 938 |
Proposed branch: | lp:~oem-qa/checkbox/patch_apport_interface_yesno |
Merge into: | lp:checkbox |
Diff against target: |
14 lines (+5/-0) 1 file modified
plugins/apport_prompt.py (+5/-0) |
To merge this branch: | bzr merge lp:~oem-qa/checkbox/patch_apport_interface_yesno |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Daniel Manrique (community) | Approve | ||
Review via email: mp+38859@code.launchpad.net |
Description of the change
ui_question_yesno method added to ApportInterface class
This method can be used both by hooks and symptom files. If any of them tries to call that method when reporting a bug from checkbox using apport, then a NotImplementedError exception will be raised and the bug won't be reported.
To post a comment you must log in.
apport_prompt.py defines ApportUserInterface as a subclass of UserInterface. As per apport. ui.UserInterfac e documentation:
A concrete subclass must implement all the abstract ui_* methods.
While not all ui_* methods are actually implemented in ApportUserInter face, it's good to advance towards completion. This code basically does that. I checked that it doesn't interfere otherwise with Checkbox operations, and also that it merges cleanly against latest trunk (as of 2011-06-28). So I'd say this is OK to merge.