Le 18/03/2021 à 15:33, Steve Dower a écrit :
On 18Mar2021 1026, M.-A. Lemburg wrote:
By having an automated infrastructure which can deal with handling the compilation step, we make things easier for C extension developers across the board and without having to restrict the C API to result in a stable ABI.
Personally, I think that we should all switch over to the conda infrastructure to get us there quickly. Others will disagree, of course, and rather continue reinventing wheels :-) That's fair.
By "conda infrastructure" I assume you mean conda-forge? So essentially standardise extension module (and package) building across the ecosystem, and establish a community that helps maintain this *apart* from the original package developers?
Not necessarily apart. I don't have a representative sample, but in my experience maintainers of conda-forge packages are often also upstream developers.
In other words, conda-forge has a rather loose model, it is not a heavily-curated distribution supervised by a well-identified organization or community that takes responsibility for the overall package set.
Regards
Antoine.
I'm not totally against this, FWIW, I just think it's unlikely that we'd get it to work (at least with the blessing of the upstream package developers, who always seem to insist on being in full control of their packages).
I would love to be convinced it could be done though :) What would it take? Am I just being too pessimistic?
Cheers, Steve
capi-sig mailing list -- capi-sig@python.org To unsubscribe send an email to capi-sig-leave@python.org https://mail.python.org/mailman3/lists/capi-sig.python.org/ Member address: antoine@python.org