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:
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?
|
[[package]] |
|
name = "pyo3" |
|
version = "0.29.0" |
|
pyo3 = { version = "0.29", features = ["abi3", "abi3t"] } |
Hopefully answer may potentially help prevent this kind of issues in the future.
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:
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?
cryptography/Cargo.lock
Lines 254 to 256 in ffde75a
cryptography/Cargo.toml
Line 33 in ffde75a
Hopefully answer may potentially help prevent this kind of issues in the future.