On Sun, 2003-04-13 at 15:54, Tim Peters wrote: > Given this, there's approximately no chance gc *caused* it. Who's been > mucking with function calls (or maybe the eval loop) recently? > We've had a lot of changes to the function call implementation over the last couple of months. What's the chance that this is just the first time we've noticed the problem? Seems pretty plausible that the recent GC changes just exposed an earlier bug. Jeremy
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