symbol not found in flat namespace '_PyBaseObject_Type' when doing cargo bench

[andresliszt]

Hello! I open this as a question, I don't think it's a bug and should be something I'm doing wrong. I have a project with pyo3 and cargo build, cargo test and also calling my rust function from python are working ok. My problem is when I do cargo bench to run some benches with criterion, so I think the binary that runs my benchmark code, which invokes the Rust code with pyo3 needs to find libpython and is not being found properly. I've read about some env vars DYLD_LIBRARY_PATH that must point to my current virtual env, but it doesn't work for me. If this is a common issue would be very nice if you can provide me some linked issues.

cargo bench

    Finished `bench` profile [optimized] target(s) in 1m 09s
     Running unittests src/lib.rs (target/release/deps/example-90dbcf98ea434473)
dyld[5634]: symbol not found in flat namespace '_PyBaseObject_Type'
error: bench failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/Users/andres.sandoval/Desktop/projects/example/target/release/deps/example-90dbcf98ea434473 --bench` (signal: 6, SIGABRT: process abort signal)

Thanks!

[peekxc]

Can confirm that outside of criterion, cargo bench seems to be incompatible with pyo3 (or vice versa). Even attempting to import only rust code fails here.

[nishaq503]

I have been seeing the same error for one of my packages, only on MacOS and not on other platforms. I found that it went away after I removed the extension-module feature for pyo3 from Cargo.toml.

[peekxc]

Well, that would be an issue for me because I need to build extension modules.

[davidhewitt]

As of PyO3 0.26, you can remove the extension-module feature and instead rely on maturin or setuptools-rust to set this when packaging (via the PYO3_BUILD_EXTENSION_MODULE env var).