> >>Therefore, I hereby propose to remove this frame field, > >>in order to save space. > ... > > > I notice that all the places that use f_tstate are functions that get > > a frame passed in. What makes you believe that those always run in > > the same thread where the frame was created? > > Schluck! > I assumed that f_tstate was just some cache, and one would > never try to look into a different thread. > This was a wrong assumption. I don't know that it is. I just don't know that it isn't, either. > Sorry, I will und my changes, ASAP. Where did you make any changes? --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