> Executive Summary: obmalloc will allow more efficient GC and we > should try hard to get it into 2.1. Can you do it before the 2.1b1 release? We're planning that for this Thursday, May 1st. Three days! > Is the only issue with obmalloc treading? If so, what do we do to > resolve this? 1. Yes, I think so. 2. It currently relies on the global interpreter lock. That's why we want to make it an opt-in configuration option (for now). Does that work with your proposed GC integration? --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