-
Notifications
You must be signed in to change notification settings - Fork 159
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
(chore): adopt scientific python deprecation schedule #1768
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1768 +/- ##
==========================================
- Coverage 83.84% 83.67% -0.17%
==========================================
Files 41 40 -1
Lines 6288 6242 -46
==========================================
- Hits 5272 5223 -49
- Misses 1016 1019 +3
|
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.
Looks really good! So many simplifications. I have a few minor questions and nitpicks apart from #1768 (comment), that’s all.
…m:scverse/anndata into ig/scientific_python_deprecation_schedule
This PR forces us to adopt the scientific python deprecation schedule as much as possible. It also cleans up our use of spmatrix/sparray because of the bumping of
scipy.sparse
so that handlingsparray
is always done via a concrete classspmatrix
andsparray
#1649