-
-
Notifications
You must be signed in to change notification settings - Fork 131
MNT: sparse
import refactor
#695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Test Results44 tests - 6 063 31 ✅ - 5 954 37s ⏱️ - 10m 3s Results for commit 2dab3d2. ± Comparison against base commit 38d1a67. This pull request removes 6107 and adds 44 tests. Note that renamed tests count towards both.
This pull request removes 122 skipped tests and adds 13 skipped tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
4aec17f
to
491af3a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can run the test suite twice, once for Finch and once for Numba in CI, without doing the importlib.reload(...)
magic? And provide a ./test.sh
script?
Done! I run tests twice in the CI with different backends: - name: Run tests
run: |
SPARSE_BACKEND=Numba pytest --pyargs sparse
SPARSE_BACKEND=Finch pytest --pyargs sparse/tests For Numba we run all tests. For Finch only the common ones. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM! Thanks so much for working on this, @mtsokol!
Hi @hameerabbasi,
This PR refactors
sparse
importing mechanism. It enforces backend selection at the import time and allowsfrom sparse import COO
etc. imports.