gh-137058: use __STDC_VERSION__ >= 202311L instead of __STDC_VERSION__ > 201710L

[Abdoulrasheed]

Updates the preprocessor check in pyport.h to use C23 __STDC_VERSION__ value (202311L)

Issue: pyport.h: use STDC_VERSION >= 202311L instead of STDC_VERSION > 201710L

• Issue: pyport.h: use __STDC_VERSION__ >= 202311L instead of __STDC_VERSION__ > 201710L #137058

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

[picnixz]

@hugovk Your pick on whether you want this to be backported. It's not really an issue but it helps reducing the diff between 3.14 and 3.15.

[vstinner]

IMO it's worth it to backport the change, but it can wait for Python 3.14.1.

[miss-islington-app]

Thanks @Abdoulrasheed for the PR, and @picnixz for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

[miss-islington-app]

Sorry, @Abdoulrasheed and @picnixz, I could not cleanly backport this to 3.14 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker cfd6da849a3c40904cddd23ae1700605877673fb 3.14

[vstinner]

I created #137409 to update _Py_NULL in the 3.14 branch.

[serhiy-storchaka]

Reminder about backporting. @Abdoulrasheed @picnixz

[vstinner]

Reminder about backporting. @Abdoulrasheed @picnixz

I created a backport to 3.14. Do you mean that we should backport the change to 3.13 as well?

[serhiy-storchaka]

There was only label for 3.14.