On Sun, Mar 19, 2006, 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. -1 -- I occasionally use exceptions as a multi-loop break. That's a perfectly valid Python practice, those exceptions should inherit from Exception, and there should not be any warnings raised. -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ "19. A language that doesn't affect the way you think about programming, is not worth knowing." --Alan Perlis
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