Timeline for Why raise an exception if python raises it for me?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 30, 2016 at 16:59 | vote | accept | user2738698 | ||
| Sep 26, 2016 at 15:59 | history | tweeted | twitter.com/StackProgrammer/status/780436599972696065 | ||
| Sep 26, 2016 at 6:33 | answer | added | amon | timeline score: 2 | |
| Sep 26, 2016 at 4:31 | answer | added | David Hammen | timeline score: 3 | |
| Sep 26, 2016 at 4:30 | answer | added | Harshit Malhotra | timeline score: -1 | |
| Sep 26, 2016 at 2:12 | answer | added | enderland | timeline score: 6 | |
| Sep 25, 2016 at 23:38 | history | edited | Tulains Córdova |
edited tags
|
|
| Sep 25, 2016 at 22:41 | comment | added | Robert Harvey | In the general sense, you catch the exception and raise a new one if you want to translate it to a more specific exception and/or if you want to do something here first (like write a log entry) and then rethrow. | |
| Sep 25, 2016 at 22:40 | comment | added | user2738698 |
@enderland in the general sense. I provided an example because people like examples and signs of effort to think about the problem here.
|
|
| Sep 25, 2016 at 22:35 | comment | added | Robert Harvey | You can certainly do that. But the error message isn't going to be as helpful as 'you never registered that item.' Instead It will be something along the lines of 'key not found in collection,' which is going to be meaningless to a user if the error is being displayed in the UI. | |
| Sep 25, 2016 at 22:34 | comment | added | enderland | Are you asking in a generalized sense or specific for this situation? | |
| Sep 25, 2016 at 22:28 | history | asked | user2738698 | CC BY-SA 3.0 |