-
-
Notifications
You must be signed in to change notification settings - Fork 32k
WASM build scripts don't honour --with-pydebug
from build-python due to a sysconfig
regression
#131769
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.
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
Comments
This was referenced Mar 26, 2025
--with-pydebug
from build-python due to sysconfig
regression--with-pydebug
from build-python due to a sysconfig
regression
I think it's fine to call the build Python and just have it exit with 1 or 0 based on whether it's a debug build to avoid any future regressions: |
brettcannon
added a commit
to brettcannon/cpython
that referenced
this issue
May 14, 2025
…en building for WASI
I now have a PR for |
brettcannon
added a commit
that referenced
this issue
May 22, 2025
--with-pydebug
from build-python due to a sysconfig
regression--with-pydebug
from build-python due to a sysconfig
regression
brettcannon
added a commit
that referenced
this issue
May 22, 2025
…hen building for WASI (GH-133219)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
2950bc5 inadvertently caused
-pydebug
to no longer be appended topybuilddir.txt
.Since the WASM build scripts look for it on the build-python's
pybuilddir.txt
to decide whether or not to configure the host with--with-pydebug
, they stopped honoring the build-python configuration.I noticed this when I unintentionally fixed it in GH-131761, which uncovered another issue, GH-130397.
CPython versions tested on:
3.14, CPython main branch
Operating systems tested on:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: