python -m arrayfire.tests fails because tests directory is not under arrayfire
savvyyabby opened this issue · comments
Simple one... in the current release the "tests" folder is not under arrayfire directory so the command
python -m arrayfire.tests
fails with a module not found error
Moving tests directory into arrayfire fixes that issue to make it consistent with the documentation
Without any change... the command
python -m tests
works fine... so maybe change the documentation?
pretty obvious 'python -m tests' is the solution