Timeline for Try-except decorator for classmethods
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2020 at 7:51 | comment | added | M Juckes |
I think you can use the above answer with a slight modification: define your decorator (using the coding advice above) but only use it on the definition of main. You would might still need an additional mechanism to handle errors that can occur during import game (e.g. when importing dependencies) -- but imports could be placed inside the definition of main.
|
|
| Sep 3, 2015 at 11:54 | comment | added | Ethan Bierlein |
I agree with all the suggestions here, except for the first one. I can't just do a "top-level" try/except because firstly, we can't just expect the user to wrap their code in a try-except block, and again, errors can occur before a GAME.play_game() is called. See shearofdoom.github.io/Cactus/Docs/v0.2.x-alpha/FirstGame
|
|
| Jun 12, 2015 at 14:42 | vote | accept | Ethan Bierlein | ||
| Jun 12, 2015 at 10:38 | history | edited | Gareth Rees | CC BY-SA 3.0 |
note about ISO 8601
|
| Jun 12, 2015 at 10:09 | history | answered | Gareth Rees | CC BY-SA 3.0 |