[issue46640] Python can now use the C99 NAN constant or __builtin_nan()

[STINNER Victor]

STINNER Victor  added the comment:

PEP 7 has been updated, I close the issue.

--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46640] Python can now use the C99 NAN constant or __builtin_nan()

[Petr Viktorin]

Petr Viktorin  added the comment:

> IMO this PEP is outdated for a long time.

It is not. Even if it is, it should be marked as such, and that is not a 
decision that should be done in this issue.

Please, don't break the rules because you think they're outdated.

> Well, if you ask me, I would simply require a C99 compiler. That's all :-)

Please propose that change. Perhaps it would be a good change to make, but I 
don't even know how to determine that.
Nor can I list the places where the change should be made -- at least there 
should be a What's New entry like 
https://docs.python.org/3.10/whatsnew/3.6.html#build-and-c-api-changes

> Note: Python uses C11 , but it remains an optional requirement.

That's fine. You can still build with an older compiler.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46640] Python can now use the C99 NAN constant or __builtin_nan()

[STINNER Victor]

STINNER Victor  added the comment:

> Well, if you ask me, I would simply require a C99 compiler. That's all :-)

Done in https://github.com/python/peps/pull/2309

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46640] Python can now use the C99 NAN constant or __builtin_nan()

[STINNER Victor]

STINNER Victor  added the comment:

> Adding new C99 features needs a change in PEP 7 
> (https://www.python.org/dev/peps/pep-0007/#c-dialect)

IMO this PEP is outdated for a long time.

C99 standard is wide. Do we have to explicitly list every single function, 
macro or constant used by Python? It doesn't sound reasonable to me. IMO saying 
that we use "C99 except of these few features: <...>" would be closer to the 
reality. I don't know which features are not used.

Well, if you ask me, I would simply require a C99 compiler. That's all :-)

Note: Python uses C11 , but it remains an optional requirement.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46640] Python can now use the C99 NAN constant or __builtin_nan()

[Petr Viktorin]

Petr Viktorin  added the comment:

Adding new C99 features needs a change in PEP 7 
(https://www.python.org/dev/peps/pep-0007/#c-dialect)

--
nosy: +petr.viktorin
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46640] Python can now use the C99 NAN constant or __builtin_nan()

[STINNER Victor]

STINNER Victor  added the comment:

I merged my change, thanks for the reviews.

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
title: Python can now use the C99 NAN constant -> Python can now use the C99 
NAN constant or __builtin_nan()

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com