Repository navigation
Bump pyo3 to v0.29.2 in Cargo.lock for next v50.0.x #15543
Description
Would it be possible to release v50.0.x with pyo3 updated to v0.29.2 in Cargo.lock?
Or are there some other interdependencies making it not possible?
"Fix PyO3 0.29 regression with failure to link under Cygwin / MSYS2." should unlock possibility of installing cryptography package in venv under MinGW-w64 environments like MSYS2 UCRT64, which unfortunately remains broken for quite some time (and different reasons as the time passed).
Context:
- provide an opt-out of raw-dylib PyO3/pyo3#6185
- How to deal with pip in venv failing to install cryptography? msys2/MINGW-packages#28218 (starting from comment)
Side question, which may be completely silly, as I have basically no knowledge of Rust and its ecosystem (and am somewhat confused with this whole Rust-within-Python approach):
Why Cargo.lock has not been updated during v50.0.1 release preparation process considering Cargo.toml specifies 0.29 and not 0.29.0?
Lines 254 to 256 in ffde75a
Line 33 in ffde75a
Hopefully answer may potentially help prevent this kind of issues in the future.
Activity
alex commentedon Aug 28, 2026
We don't generally backport any changes to our release branches besides those addressing the purpose of the release. In this case our only 50.0.x release was for the purpose of bumping OpenSSL, so we didn't make any changes to our rust dependencies.
If we do a further 50.0.x releaes, I'm fine backporting the pyo3 bump for it.
[50.0.x] Bump pyo3 to 0.29.2 (#15731)