Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Deprecate `cupy.sparse` package
See original GitHub issueRel #3420.
CuPy’s sparse matrix feature was initially implemented as cupy.sparse package, and is moved to cupyx.scipy.sparse package with keeping cupy.sparse for backward compatibility.
Is it good time to deprecate cupy.sparse package?
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Possible issue with cupy sparse? #1261 - GitHub
Hi there, I am trying to build a sparse matrix using Cupy. ... DeprecationWarning: Numeric-style type codes are deprecated and will result ...
Read more >Upgrade Guide — CuPy 11.4.0 documentation
This replaces per-CUDA version binary packages ( cupy-cuda112 ... cupy.sparse module has been deprecated and will be removed in future releases.
Read more >Released CuPy v8.0.0rc1 - Google Groups
CuPy for CUDA 11.0 ( cupy-cuda110 ) wheel packages are currently available only for Windows. ... Deprecate cupy.sparse package (#3839, #3856).
Read more >scipy.sparse.csr_matrix — SciPy v1.9.3 Manual
If the shape parameter is not supplied, the matrix dimensions are inferred from the index arrays. Notes. Sparse matrices can be used in...
Read more >cuSPARSE - NVIDIA Documentation Center
The API reference guide for cuSPARSE, the CUDA sparse matrix library. ... Level 2: operations between a matrix in sparse format and a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I like it. I think one full release cycle then deprecation is a fair amount of time to give users, especially if it is clearly noted in cupy 8 release notes.
@jakirkham Thank you for the quick actions!
cupy.cusparseremains as is.I think raiseing deprecation warning in v8rc1 and remove in v9 is the best, but if you have concerns we can delay the deprecation.