Avoid requiring editable builds (`-e`) for running tests

[leofang]

Right now it is quite subtle that the test/benchmark suites are designed to only allow editable builds to run. For normal builds, pytest has a hard time importing the needed modules. I stumbled over this for a few times.

cuda-python/docs_src/source/install.md

Line 65 in e1e3325

pip install -e .

This should be fixed.

[leofang]

Not sure if this is related, but instead of the current layout for tests/examples/benchmarks

• cuda/setup.py
• cuda/cuda/bindings/tests
• cuda/cuda/bindings/examples
• cuda/cuda/bindings/benchmarks

ideally the layout should have been made such that they are outside of source tree and living side-by-side with setup.py for the package, so

• cuda/setup.py
• cuda/cuda/bindings/
• cuda/tests
• cuda/examples
• cuda/benchmarks

I probably made a bad mistake back then (leofang#1) 😓

cc @vzhurba01

[vzhurba01]

Resolved by MR #159. Updated cuda-python/cuda/README.md with how to run.

The final commands are:
Command to test against in-tree builds:

• unittests: cuda-python/cuda_bindings$ python -m pytest tests/
• samples: cuda-python/cuda_bindings$ python -m pytest examples/

Command to test against distributable package (wheels/conda)

• unittests: cuda-python/cuda_bindings$ pytest tests/
• samples: cuda-python/cuda_bindings$ pytest examples/

Closing.