Skip to content
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

Track Numba failures coming from Sparse+NumPy 1.17 #4994

Closed
pentschev opened this issue Jun 24, 2019 · 2 comments
Closed

Track Numba failures coming from Sparse+NumPy 1.17 #4994

pentschev opened this issue Jun 24, 2019 · 2 comments
Labels

Comments

@pentschev
Copy link
Member

This is an issue that happens on the upstream builds, as noticed in #4961 by @TomAugspurger .

There's currently an open issue for that in pydata/sparse#257, and it only happens when NumPy master (pre-1.17) is used with Sparse.

@jakirkham
Copy link
Member

Do these still happen in NumPy 1.18 or later?

@pentschev
Copy link
Member Author

No, I don't think so. According to pydata/sparse#257 (comment) the issue was resolved by numba/numba#3953. This was probably just forgotten open here but it should be safe to close now. Thanks for tracking this @jakirkham .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants