> There's a buglet in my assignable __bases__ code that can (in pretty > obscure situations) lead to Python code getting executed with an > exception pending. I have a fix, but I'd like a test -- can anyone > think of a way of testing for this? I was going to suggest a __del__ method, except that doesn't work -- the code that calls __del__ is very careful to save and restore exceptions around the call. I think you're talking about the code near the end of type_set_bases(). I still don't understand why you can'y just bail out? --Guido van Rossum (home page: http://www.python.org/~guido/)
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