-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
maturin build --sdist
: README.md was already added for workspace crate
#2244
Comments
What is ETA for this? (no pressure intended) |
See PyO3/maturin#2244 for more details
See PyO3/maturin#2244 for more details
The test crate still needs to be wired up Fixes #2244
Thank you, @konstin! 😃 🍰 |
Readme nesting was broken post 1.6.0: PyO3/maturin#2244
I managed to run into this issue running on the bug-fixed v1.7.5
I reverted back to v1.6.0 and it was working once again. I did double check and this issue was fixed in #2262 and mentioned in the v1.7.5 release but it seems like the issue is still present. |
I also encounter this issue with version v1.7.5 if I have [project]
readme = "README.md" in the |
Is this fixed on v1.7.7? |
I'm still seeing the issue with version @konstin I think this issue shouldn't be closed. |
I opened a new issue for this. Give a thumbs up. |
Bug Description
With a README file both in the workspace root and the crate root:
building a source distribution fails:
Cargo.toml, mitmproxy-rs/Cargo.toml, and mitmproxy-rs/pyproject.toml do not specify any (custom) settings w.r.t. READMEs. I would have expected maturin to use
mitmproxy-rs/README.md
and notREADME.md
.This is a regression that started in 1.7.1. Refs #2184 and #2154.
Your maturin version (
maturin --version
)1.7.4
Your Python version (
python -V
)3.12
Your pip version (
pip -V
)all
What bindings you're using
pyo3
Does
cargo build
work?The text was updated successfully, but these errors were encountered: