> I assigned bug 411881 to myself today and started looking through things to > at least try to whittle down the number of cases that need to be considered. > Almost immediately I came across this code in anydbm.py: > > try: > class error(Exception): > pass > except (NameError, TypeError): > error = "anydbm.error" > > Is this sort of construct really necessary? It doesn't seem that > any other exception definitions in the standard library fall back to > string exceptions. This must hark back to the days when there was a command line option (-X) to make all built-in exceptions string exceptions. The last release that supported this was 1.5.2. So please get rid of it! --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4