Skip to content

Distinguish between pyodide-build and pypa/build as build frontends when handling build verbosity#2609

Draft
agriyakhetarpal wants to merge 5 commits intopypa:mainfrom
agriyakhetarpal:pyodide-build-verbosity-handling
Draft

Distinguish between pyodide-build and pypa/build as build frontends when handling build verbosity#2609
agriyakhetarpal wants to merge 5 commits intopypa:mainfrom
agriyakhetarpal:pyodide-build-verbosity-handling

Conversation

@agriyakhetarpal
Copy link
Member

@agriyakhetarpal agriyakhetarpal commented Sep 29, 2025

@agriyakhetarpal agriyakhetarpal force-pushed the pyodide-build-verbosity-handling branch from fad4b7d to ff45d5c Compare September 29, 2025 22:54
@agriyakhetarpal agriyakhetarpal changed the title Distinguish between pyodide-build and pypa/build as build frontends Distinguish between pyodide-build and pypa/build as build frontends when handling build verbosity Sep 29, 2025
@agriyakhetarpal
Copy link
Member Author

I don't think this is the right approach at the moment, and I should try another way. What I think happens here is that _get_verbosity_flags will get wrapped in get_build_frontend_extra_flags, which will be called at the time of Pyodide builds. However, the finalisation of the build frontend flags happens outside and before the pyodide build command is called, which means the PYODIDE environment variable is set during the wheel builds and not when cibuildwheel performs its own preparation for the build, which means that this will fail to remove the verbosity-related flags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments