At 01:02 PM 6/26/04 +0200, Martin v. Löwis wrote: >It seems that Guido has attempted to clarify it as "an exception is active >until the next exception is raised, or the program terminates". > >However, that clarification doesn't describe the current implementation, >atleast not for interactive mode: > > >>> try: >.. 1/0 >.. except: >.. pass >.. > >>> raise >Traceback (most recent call last): > File "<stdin>", line 1, in ? >TypeError: exceptions must be classes, instances, or strings (deprecated), >not NoneType > >Here, the re-raise doesn't find an exception anymore, even >though non has been raised... Isn't each statement/block in the interactive interpreter run in a new frame?
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