Hi,
Le sam. 6 juin 2020 à 13:50, Stefan Behnel <python_capi@behnel.de> a écrit :
Now, whether this is done via a header file that users can copy over entirely or selectively, or by documenting newly added stuff in a way that makes it easy to find and copy, I don't mind. I personally think it's easier to keep these things under local VC rather than as a dependency, but that might just be me.
I'm fine with people who only copy/paste a few functions that they need, directly in their C code. It's the most convenient option to *install* a C extension. But it may make maintenance harder if more and more compatibility code is needed in the future.
I think it could be helpful if CPython maintained such a header file in its repo, with the appropriate version guards in it. Then users can decide whether they want to copy the whole file or just bits from it.
I propose to start in a separate repository, and we can decide later to move it into the Python repository.
Right now, the scope and goals of this https://github.com/pythoncapi/pythoncapi_compat is still blurry to me :-)
Victor
Night gathers, and now my watch begins. It shall not end until my death.