`setup.py develop` blocks later usage of optimized builds

[pyo3]

`setup.py develop` blocks later usage of optimized builds

[clbarnes]

Related:

By default, develop will create a debug build, while install will create a release build.

Is it possible to customise this when calling e.g. setup.py test? Our use case is that we want pytest to run our benchmarks, but some combination of pytest's path mangling and setuptools-rust's build configuration makes it impossible to read the optimized version of our library from site-packages.

[althonos]

Hi @clbarnes ,

I don't have a good solution for this, given the compiled binary must be copied to the build directory in a location setuptools is expecting it, so there's no way to really check with which profile a binary was built.

However, you can force the compilation in debug or release mode using the build_rust subcommand:
python setup.py build_rust -r develop will compile in release mode before using develop, or python setup.py build_rust -r install to make sure you always install the release binary.

[clbarnes]

Great, that should do fine!