Skip to content

stop inlining config into pyo3-build-config; generate directly in pyo3-ffi#5862

Draft
davidhewitt wants to merge 15 commits intoPyO3:mainfrom
davidhewitt:build-config-no-resolve
Draft

stop inlining config into pyo3-build-config; generate directly in pyo3-ffi#5862
davidhewitt wants to merge 15 commits intoPyO3:mainfrom
davidhewitt:build-config-no-resolve

Conversation

@davidhewitt
Copy link
Copy Markdown
Member

This is an experiment to simplify pyo3-build-config to not have a build.rs itself, and let pyo3-build-config do the hard work. Instead, callers of pyo3-build-config APIs must themselves have a direct dependency on pyo3 or pyo3-ffi to pull information via env vars propagated by cargo.

I suspect that this will make integration of pyo3 with e.g. meson-python significantly easier, see e.g. mesonbuild/meson-python#721 (comment)

I also hope that it will enable faster CI; pyo3-build-config itself should now never need to rebuild when switching between abi3 / non-abi3.

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

Labels

CI-build-full CI-no-fail-fast If one job fails, allow the rest to keep testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant