Timeline for Most Pythonic way to do input validation
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2020 at 9:12 | history | edited | Community Bot |
Commonmark migration
|
|
| Dec 12, 2013 at 16:59 | comment | added | eyquem | @henrebotha I got a strong simplification | |
| Dec 12, 2013 at 16:57 | history | edited | eyquem | CC BY-SA 3.0 |
added 826 characters in body
|
| Dec 12, 2013 at 16:22 | comment | added | eyquem | What is somewhat horrid is the way I must follow to find the function whose result has caused the Assertion error: traceback object converted to a string, regex searching in this string, passing the group to glabals to find the function object, getting the doc of the function ! I didn't succeed to extract the function or its name more directly from the traceback object. - But the basic idea may be interesting: conditional functions can be added simply without changing the except block. | |
| Dec 12, 2013 at 16:12 | comment | added | henrebotha | Interesting indeed, but very complicated for routine tasks, I think. | |
| Dec 12, 2013 at 15:16 | history | answered | eyquem | CC BY-SA 3.0 |