Repository navigation
test_xxlimited is skipped on Windows in debug mode #161724
Description
Example on a recent GitHub Action job: https://github.com/python/cpython/actions/runs/42723050421
- Windows / Build and test (x64, switch-case):
3 tests skipped: test_curses test_xxlimited test_xxtestfuzzwith== Python build: debug-- test_xxlimited is skipped - Windows / Build and test (x64, tail-call):
2 tests skipped: test_curses test_xxtestfuzzwith== Python build: release
xxlimited extensions are only built in Release mode by PCbuild/pcbuild.proj:
<TestModules Include="xxlimited" Condition="'$(Configuration)' == 'Release'" />
<TestModules Include="xxlimited_35" Condition="'$(Configuration)' == 'Release'" />
<TestModules Include="xxlimited_3_13" Condition="'$(Configuration)' == 'Release'" />
I propose to build the xxlimited extensions in Debug mode as well.
Activity
zooba commentedon Nov 10, 2026
Presumably there was a reason for this? Any indication (either in the code or in the commit history) why it was done this way?
vstinner commentedon Nov 10, 2026
It's uneasy to remind the status of the limited C API and the stable ABI ... 12 years ago! (65e4cb1) Let's say that it's now better supported on all platforms and I see no reason to only skip test_xxlimited on Windows built in debug mode :-)
zooba commentedon Nov 10, 2026
It looks like that commit also added the Debug configuration to python3dll, so probably the condition to exclude it was carried over from the earlier build system that didn't include a Debug build at all.
gh-161724, PCbuild: Build also xxlimited in Debug configuration (#161725
[3.15] gh-161724, PCbuild: Build also xxlimited in Debug configuration (
[3.14] gh-161724, PCbuild: Build also xxlimited in Debug configuration (
pythongh-161724, PCbuild: Build also xxlimited in Debug configuration (…