On Fri, Jun 17, 2022 at 6:16 PM Marc-Andre Lemburg <mal@egenix.com> wrote:
With a proper reporting process in place, we'll get communication going between extension writers and core devs and without alienating the extension writers, or making assumptions which don't hold in practice.
There are issues, capi and python-dev mailing lists, and https://discuss.python.org/ It's not enough?
IMO What's New in Python now better documents incompatible C API changes than previously. We are paying more attention to documenting these changes.
I have a feeling that such communication is not really working out.
Would you mind to be more specific?
I keep monitoring changes to the APIs and raise concerns where needed in areas where I know they are going to cause problems, but that's only one set of eyes. We need plenty more.
There are more and more people running code search in advance, and paying a close attention to projects testing the "next Python" (like Python 3.12 today). My feeling is like more people are proactive to research for issues and reports them. But it seems like you have a different experience.
This will benefit both core devs and extension writers, since only a healthy and reasonably complete Python C API will help sustain the popularity and attractiveness of Python in areas which are far away from core development - e.g. most of the PyData or scientific space.
I'm not sure what do you propose in practice?
Victor
Night gathers, and now my watch begins. It shall not end until my death.