New submission from Nick Coghlan <ncogh...@gmail.com>:
The Porting section of the What's New guide is for changes where the old behaviour was at best arguably correct, but it's still possible someone was relying on it behaving exactly the way it used to. It isn't for us to say "We broke all extensions that use this existing public C API by adding a new parameter to its signature". For 3.8b2, the function with the extra parameter should be renamed to PyCode_NewEx, and a PyCode_New compatibility wrapper added that calls it with the extra parameter set to zero. ---------- keywords: 3.8regression messages: 345153 nosy: lukasz.langa, ncoghlan, pablogsal priority: release blocker severity: normal stage: needs patch status: open title: PyCode_New API change breaks backwards compatibility policy type: compile error versions: Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37221> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
