[Python-Dev] PEP 682: Format Specifier for Signed Zero

Just a note that this PEP is being discussed at https://discuss.python.org/t/pep-682-format-specifier-for-signed-zero TLDR; When formatting a number (especially with rounding options), often you don't want negative-signed zero as an output. A format spec extension enables normalizing such

[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: Steering Council reply to PEP 670 -- Convert macros to functions in the Python C API

On Wed, 9 Feb 2022 17:49:19 +0100 Victor Stinner wrote: > On Wed, Feb 9, 2022 at 1:04 PM Petr Viktorin wrote: > > > Right now, a large number of macros cast their argument to a type. A > > > few examples: > > > > > > #define PyObject_TypeCheck(ob, type) > > >

[Python-Dev] Re: Require a C compiler supporting C99 to build Python 3.11

On Wed, 09 Feb 2022 03:39:42 - h.vetin...@gmx.com wrote: > > That is becoming dated quickly, as Microsoft has deprecated, and is removing, > that version quite rapidly from their CI services (azure/GHA), i.e. mid > March, see: > https://github.com/actions/virtual-environments/issues/4312. >