On 10/28/05, Raymond Hettinger <raymond.hettinger at verizon.net> wrote: > I don't follow why the PEP deprecates catching a category of exceptions > in a different release than it deprecates raising them. Why would a > release allow catching something that cannot be raised? I must be > missing something here. Presumably because they CAN still be raised; attempting to do so provokes a warning, not an error. It also facilitates upgrading from old versions of Python. You can work to eliminate cases where the exceptions are raised while still handling them if they do get raised. -- Adam Olsen, aka Rhamphoryncus
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