Guido van Rossum wrote: > Some extensions will break because they don't use the right > alloc/dealloc macros (we just fixed a few of these in Zope) A lot of extensions will break. The example code in xxmodule.c was "wrong" for years. > alpha time is a good time to start fortcing this issue. A big warning > in NEWS might be useful. If we don't want to create yet another memory management API then that's the right approach. Personally, I don't mind enabling pymalloc without changing the API. However, I suspect I'm better at debugging memory management bugs than the average Python user. I'm afraid users are going to be upset when they upgrade to 2.3 and things start crashing because they are using some broken extension modules. Neil
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