-
Notifications
You must be signed in to change notification settings - Fork 112
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
MSRV for rust-numpy #176
Comments
Ah, sorry for my laziness about it and thank you for letting me know that!
|
@mtreinish |
If we put We could test this in CI with an example. |
@kngwyu I think changing the ndarray dependency to One other place we might need to loosen the requirements in rust-numpy is num-complex. ndarray 0.13 uses num-complex 0.2: https://github.com/rust-ndarray/ndarray/blob/0.13.1/Cargo.toml#L33 while we have num-complex = 0.3. Things for me compile fine locally and cargo just builds with num-complex 0.2 for ndarray and 0.3 for rust-numpy, but I haven't tested anything which uses complex numbers so I'm not sure if there will be a version mismatch for users that use arrays with complex numbers. |
Ah, OK, thank you both for pointing it out! |
Released 0.13.1, which would work with Rust 1.41.1. |
Following PyO3/pyo3#1420 and PyO3/pyo3#1431 PyO3's MSRV is 1.41. Right now rust-numpy advertises the msrv of 1.39 in the README, but because ndarray 0.14 is listed as a dependency the functional msrv is 1.42 since the ndarray 0.14 release bumped their msrv (https://github.com/rust-ndarray/ndarray/blob/master/RELEASES.md#other-changes-1 )
I'm hoping to clarify the rust-numpy MSRV policy because this is blocking me from upgrading pyo3 (see: Qiskit/rustworkx#238 ) because I'm trying to maintain rust 1.41 compatibility for debian users. Once the policy is clarified for rust-numpy we can add a CI job to enforce it like we have in pyo3.
The text was updated successfully, but these errors were encountered: