On Thu, Feb 24, 2022 at 3:27 PM Victor Stinner wrote:
> On Thu, Feb 24, 2022 at 11:10 PM Barry wrote:
> > > "Python 3.11 and newer versions use C11 without optional features. The
> > > public C API should be compatible with C++."
> > > https://github.com/python/peps/pull/2309/files
> >
> >
The consensus is to require IEEE 754 to build CPython, but not require
it in the Python language specification.
Updates (changed merged in bpo-46656):
* Building Python 3.11 now requires a C11 compiler without optional
C11 features. I wrote it in What's New in Python 3.11 and the PEP 7.
*
On Thu, Feb 24, 2022 at 11:10 PM Barry wrote:
> > "Python 3.11 and newer versions use C11 without optional features. The
> > public C API should be compatible with C++."
> > https://github.com/python/peps/pull/2309/files
>
> Should is often read as meaning optional when writing specs.
> Can you
> On 24 Feb 2022, at 11:45, Victor Stinner wrote:
>
> Ok, let me try something simpler:
>
> "Python 3.11 and newer versions use C11 without optional features. The
> public C API should be compatible with C++."
> https://github.com/python/peps/pull/2309/files
Should is often read as meaning
Hi all,
This is specifically about embedding Python on Windows, and I'm hoping some of
the Windows Python devs might have some ideas or be interested in this. I have
implemented a partial solution (linked below) and I'm interested to hear what
other people think of this.
Currently when
Ok, let me try something simpler:
"Python 3.11 and newer versions use C11 without optional features. The
public C API should be compatible with C++."
https://github.com/python/peps/pull/2309/files
Victor
___
Python-Dev mailing list --
On 23. 02. 22 20:15, Victor Stinner wrote:
On Wed, Feb 23, 2022 at 7:11 PM Petr Viktorin wrote:
I did realize there's one more issue when converting macros or static
inline functions to regular functions.
Regular functions' bodies aren't guarded by limited API #ifdefs, so if
they are part