-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
Open
Labels
OS-windowsbuildThe build process and cross-buildThe build process and cross-buildextension-modulesC modules in the Modules dirC modules in the Modules dirtopic-sysconfigtype-featureA feature request or enhancementA feature request or enhancement
Description
Feature or enhancement
Proposal:
Currently, the sys.abiflags
attribute is only set on Unix systems. On Windows, there are no sys.abiflags
set (i.e. hasattr(sys, 'abiflags') -> False
). It is hard to tell if Python is in free-threaded or debug builds. Although developers can use something like sysconfig.get_config_var('Py_GIL_DISABLED')
. It is not well documented and is not convenient.
Lines 686 to 687 in 3afb639
if not sys.platform.startswith('win'): | |
self.assertIsInstance(sys.abiflags, str) |
Lines 1294 to 1297 in 3afb639
@test.support.cpython_only | |
@unittest.skipUnless(hasattr(sys, 'abiflags'), 'need sys.abiflags') | |
def test_disable_gil_abi(self): | |
self.assertEqual('t' in sys.abiflags, support.Py_GIL_DISABLED) |
It would be nice if we could set ABIFLAGS
in pyconfig.h
and enable sys.abiflags
on Windows. This would simplify much code in the wild world and also in the CPython repo.
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Linked PRs
Metadata
Metadata
Assignees
Labels
OS-windowsbuildThe build process and cross-buildThe build process and cross-buildextension-modulesC modules in the Modules dirC modules in the Modules dirtopic-sysconfigtype-featureA feature request or enhancementA feature request or enhancement