> What about recent pymalloc changes? They should yield some > performance enhancements, will make no difference to Python code, but > probably require cooperation from extension authors... That would be another Project. :-( May be worth it, may be not. I'd hate to foist pymalloc on the community in 2.2.2 only to find out that it breaks in 1% of situations. It does suggest that we should try to strive for a malloc API that doesn't require changes to extensions written (according to the docs) for 2.2. --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