Fredrik Lundh wrote: > > David Ascher wrote: > > > > Makes me wonder if it makes sense to move KeyboardInterrupt up the > > hierarchy and promote the use of StandardError... > > it would have been great if it had been done that way > from the beginning, but can we really change this now? > > (if we can, +1 from here) It would be relatively simple to define a new error type which did what we wanted, and slowly deprecated StandardError. Once again, it'd be nice if all Python source ever written had to be stored somewhere so we could measure the impact of language changes. Hmm -- maybe a slight change to ceval.c and its Jython equivalent could help =) --david
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