10000 Python 3.13a4: ``_Py_atomic_load_ssize_relaxed``: identifier not found · Issue #116078 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

Python 3.13a4: _Py_atomic_load_ssize_relaxed: identifier not found #116078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wjakob opened this issue Feb 28, 2024 · 3 comments
Closed

Python 3.13a4: _Py_atomic_load_ssize_relaxed: identifier not found #116078

wjakob opened this issue Feb 28, 2024 · 3 comments
Labels
3.13 bugs and security fixes OS-windows topic-free-threading type-bug An unexpected behavior, bug, or error

Comments

@wjakob
Copy link
Contributor
wjakob commented Feb 28, 2024 •
edited by hugovk
Loading

Bug report

Bug description:

Dear CPython team,

I bumped the nanobind test suite build matrix to include 3.13a4. This works except for compilation on windows via MSVC, which fails with an error complaining that _Py_atomic_load_ssize_relaxed is not defined.

C:\hostedtoolcache\windows\Python\3.13.0-alpha.4\x64\include\object.h(433,5): error C3861: '_Py_atomic_store_ssize_relaxed': identifier not found

Link: https://github.com/wjakob/nanobind/actions/runs/8087892173/job/22100798452

I think that including Python.h from an extension is all that's needed to trigger this. I know that there has been a lot of activity in this part of the code related to free-threading. But I am not creating a free-threading build.

CPython versions tested on:

3.13, CPython main branch

Operating systems tested on:

Windows
@wjakob wjakob added the type-bug An unexpected behavior, bug, or error label Feb 28, 2024
@hugovk hugovk added the 3.13 bugs and security fixes label Feb 29, 2024
@zooba
Copy link
Member
zooba commented Feb 29, 2024

Unfortunately, due to a build issue in 3.13a4, you may still have the Py_GIL_DISABLED flag set (because it's hardcoded into the header, and the wrong header shipped - see #115582). That's likely the cause of this issue.

If you're able to, could you patch that definition (in pyconfig.h) to 0 to see if that fixes the issue? I've been building plenty of my own stuff with 3.13a4, though with a fixed build, and have not seen this particular problem.

@wjakob
Copy link
Contributor Author
wjakob commented Feb 29, 2024

I'm using the GitHub setup-python action and so have no influence over the Python package that is installed.

@zooba
Copy link
Member
zooba commented Feb 29, 2024

Then we'll have to assume this is caused by #115582 and will be fixed in the next release. It's possible to pin to an earlier alpha if you need to.

@zooba zooba closed this as not planned Won't fix, can't repro, duplicate, stale Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.13 bugs and security fixes OS-windows topic-free-threading type-bug An unexpected behavior, bug, or error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wjakob @hugovk @zooba @erlend-aasland
0