gh-142038: Expand guard for types_world_is_stopped to fix debug builds without assertions

[xhochy]

The types_world_is_stopped() function needs to be defined if NDEBUG or when we're in a debug build is not defined.

Issue:

• 3.15.0a2 doesn't compile with CFLAGS=-DNDEBUG and --with-pydebug #142038

• Issue: 3.15.0a2 doesn't compile with CFLAGS=-DNDEBUG and --with-pydebug #142038

[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]

The name of the macro is not Py_Debug but Py_DEBUG And ideally, I think we should instead use Py_DEBUG rather than NDEBUG.

[kumaraditya303]

Agreed, this should be just Py_DEBUG.

[xhochy]

We had that before, and that caused problems for non-debug builds with --with-assertions. This issue was then addressed by #140133, which, however, introduced a new problem with debug-without-assertions builds.

[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.

[vstinner]

Can someone else reproduce #142038 issue?

[vstinner]

LGTM

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x Fedora Stable Clang Installed 3.x (tier-3) has failed when building commit f6f456f.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1645/builds/1663) and take a look at the build logs.
4. Check if the failure is related to this commit (f6f456f) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1645/builds/1663

Failed tests:

• test_profiling

Failed subtests:

• test_gil_mode_integration_behavior - test.test_profiling.test_sampling_profiler.test_modes.TestGilModeFiltering.test_gil_mode_integration_behavior

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-s390x.clang-installed/build/target/lib/python3.15/test/test_profiling/test_sampling_profiler/test_modes.py", line 384, in test_gil_mode_integration_behavior
    with test_subprocess(gil_test_script) as subproc:
         ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-s390x.clang-installed/build/target/lib/python3.15/contextlib.py", line 141, in __enter__
    return next(self.gen)
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-s390x.clang-installed/build/target/lib/python3.15/test/test_profiling/test_sampling_profiler/helpers.py", line 85, in test_subprocess
    raise RuntimeError(
        f"Unexpected response from subprocess: {response!r}"
    )
RuntimeError: Unexpected response from subprocess: b'readythreads_ready'