Greg Ewing wrote: > Barry Warsaw wrote: > > > One possible approach is to revert BaseException out of Py2.5, > > re-position KeyboardInterrupt, and add Error as an alias for > > StandardError. Then we can encourage people to start using Error > > as the base classes for their own errors. > > Also maybe start issuing warnings whenever you inherit > directly from Exception. Ugh. I hate it when it's made (virtually) impossible to write code that runs warnings-free on both Python X.Y and X.(Y+1). Just
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