[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

Results of the poll (which was open for 10 days): * Move pythoncapi_compat: 19 votes (90%) * Don't move pythoncapi_compat: 2 votes (10%) Victor On Fri, Feb 11, 2022 at 12:16 AM Victor Stinner wrote: > > I created a poll on Discourse: >

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On Tue, 15 Feb 2022, 2:57 am Petr Viktorin, wrote: > >> > >> Yes. > >> On older Python versions, where the public API wasn't yet available, > >> those backports use private API. If we change the private API in a > >> point release, the backport will break. > > > > Do you have an example of this?

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 14. 02. 22 17:26, Ronald Oussoren wrote: On 14 Feb 2022, at 14:07, Petr Viktorin > wrote: On 14. 02. 22 13:37, Antoine Pitrou wrote: On Mon, 14 Feb 2022 13:19:00 +0100 Petr Viktorin mailto:encu...@gmail.com>> wrote: If we don't have much sympathy for

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

> On 14 Feb 2022, at 14:07, Petr Viktorin wrote: > > > > On 14. 02. 22 13:37, Antoine Pitrou wrote: >> On Mon, 14 Feb 2022 13:19:00 +0100 >> Petr Viktorin wrote: >>> >>> If we don't have much sympathy for projects that use private API where >>> does that leave pythoncapi_compat? >> If you

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 14. 02. 22 13:37, Antoine Pitrou wrote: On Mon, 14 Feb 2022 13:19:00 +0100 Petr Viktorin wrote: If we don't have much sympathy for projects that use private API where does that leave pythoncapi_compat? If you look at pythoncapi_compat.h, it provides backports for recently-introduced

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

Hi, On Thu, 10 Feb 2022 23:58:31 +0100 Victor Stinner wrote: > > Would it make sense to move the pythoncapi_compat project under the > GitHub Python or PSF organization to make it more "official" and a > little bit more sustainable? I'm +1 on this. Many projects maintain their own set of

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On Mon, 14 Feb 2022 13:19:00 +0100 Petr Viktorin wrote: > > If we don't have much sympathy for projects that use private API where > does that leave pythoncapi_compat? If you look at pythoncapi_compat.h, it provides backports for recently-introduced public APIs such as PyObject_CallOneArg().

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 11. 02. 22 19:25, Neil Schemenauer wrote: On 2022-02-11 06:14, Petr Viktorin wrote: Sounds reasonable, but... The implication of endorsing code like this is that *we cannot change private API even in patch releases*, which I don't think is documented anywhere, and might be a bit

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 2022-02-11 06:14, Petr Viktorin wrote: Sounds reasonable, but... The implication of endorsing code like this is that *we cannot change private API even in patch releases*, which I don't think is documented anywhere, and might be a bit controversial. I think we are still allowed to

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On Fri, Feb 11, 2022 at 3:14 PM Petr Viktorin wrote: > Sounds reasonable, but... > > The implication of endorsing code like this is that *we cannot change > private API even in patch releases*, which I don't think is documented > anywhere, and might be a bit controversial. > (I'm still planning

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 11. 02. 22 13:52, Victor Stinner wrote: On Fri, Feb 11, 2022 at 12:06 PM Petr Viktorin wrote: Or will this send a message that core devs should co-maintain the project? I personally wouldn't want to maintain it, but it it looks like there are at least 3 maintainers who do. I think that

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On Fri, Feb 11, 2022 at 12:06 PM Petr Viktorin wrote: > Or will this send a message that core devs should co-maintain the project? > I personally wouldn't want to maintain it, but it it looks like there > are at least 3 maintainers who do. I think that Neal provided a better answer than me :-)

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 10. 02. 22 23:58, Victor Stinner wrote: Hi, Would it make sense to move the pythoncapi_compat project under the GitHub Python or PSF organization to make it more "official" and a little bit more sustainable? "The pythoncapi_compat project can be used to write a C extension supporting a wide

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

On 2022-02-10 2:58 p.m., Victor Stinner wrote: Would it make sense to move the pythoncapi_compat project under the GitHub Python or PSF organization to make it more "official" and a little bit more sustainable? I think that makes sense.  Extensions typically have this kind of compatibility

[Python-Dev] Re: Move the pythoncapi_compat project under the GitHub Python or PSF organization?

I created a poll on Discourse: https://discuss.python.org/t/move-the-pythoncapi-compat-project-under-the-github-python-or-psf-organization/13651 It will be closed automatically in 10 days. Victor ___ Python-Dev mailing list -- python-dev@python.org To