> What is going to be the fate of the GC? There are currently two > reported bugs which I have been unable to reproduce. If its > going to be disabled for 2.0 then it should be disabled in the > beta release. Good point. I see only the one that's assigned to you (reported by Rob Hooft): http://sourceforge.net/bugs/?group_id=5470&func=detailbug&bug_id=115341 What's the other? Hooft's problem makes heavy use of Tkinter and Pmw, it seems. Maybe that's a clue? Does he also use threads? Is he willing to send his entire program over? (If you don't have time, we may have time at PythonLabs!) Anyway, I'm not yet ready to disable GC by default -- that's sensible but also defeats the purpose... --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