Optionally disable pyo3/auto-initialize?

[dovahcrow]

Currently, it is not possible to use rust-numpy with cargo test, due to the issue mentioned here https://pyo3.rs/v0.13.1/faq.html#i-cant-run-cargo-test-im-having-linker-issues-like-symbol-not-found-or-undefined-reference-to-_pyexc_systemerror.

This is because even one disables the corresponding auto-initialize feature for pyo3, rust-numpy still enables it.

A workaround is in my fork at here, which adds a pyo3-default feature to control the pyo3 features.

Basically, one can use the method included in the FAQ, along with adding default-features = false to the numpy crate to allow a project to run the tests successfully.

I can create a PR if you guys think this solution is acceptable.

[dovahcrow]

Also, I feel like rust-numpy does not require the auto-initialize feature anyway. So it might possible to just disable these unused default pyo3 features.

[kngwyu]

Thanks for reporting.

Doesn't the below workaround work?

[dependencies.pyo3]
version = "0.13"
default-features = false
features = ["extension-module"]

Also, I feel like rust-numpy does not require the auto-initialize feature anyway. So it might possible to just disable these unused default pyo3 features.

That's worth considering. Actually, those features were not optional until recently.

[kngwyu]

Ah, but I noticed that auto-initialize would be removed: PyO3/pyo3#1443

[dovahcrow]

@kngwyu Yep, I saw that issue just now. I think we can just wait for the upstream.

Feel free to close this issue.