chore: use scverse-misc

[ilan-gold]

• Closes #
• Tests added

• Release note not necessary because: dev change

[codecov]

Codecov Report

❌ Patch coverage is 95.83333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 85.36%. Comparing base (38b8351) to head (3f36b4e).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/anndata/types.py	92.30%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2387      +/-   ##
==========================================
- Coverage   87.46%   85.36%   -2.10%     
==========================================
  Files          49       49              
  Lines        7753     7694      -59     
==========================================
- Hits         6781     6568     -213     
- Misses        972     1126     +154     

Files with missing lines	Coverage Δ
src/anndata/_core/aligned_mapping.py	93.85% <100.00%> (-1.21%)	⬇️
src/anndata/_core/anndata.py	85.43% <100.00%> (+0.02%)	⬆️
src/anndata/_core/extensions.py	100.00% <100.00%> (+4.68%)	⬆️
src/anndata/_io/read.py	52.55% <100.00%> (+0.24%)	⬆️
src/anndata/_io/write.py	53.68% <100.00%> (+0.49%)	⬆️
src/anndata/utils.py	86.22% <ø> (-1.65%)	⬇️
src/anndata/types.py	95.00% <92.30%> (-5.00%)	⬇️

... and 7 files with indirect coverage changes

[flying-sheep]

Awesome!

We do have to take to keep the mission of scverse-misc focused though, it would be unfortunate if it sprawled to become an unmaintainable mess.

Miscellaneous utility code used by scverse packages

is a bit too broad.

I’ll file an issue!

[ilan-gold]

We do have to take to keep the mission of scverse-misc focused though, it would be unfortunate if it sprawled to become an unmaintainable mess.

Agreed I already asked that some pandas code be removed. A smell-test is that it shouldn't have dependencies like pandas unless there is an amazing reason. Super light, focused, python.

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 0.12.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 40e6ab1a4c14152955db4c8c8f6a3ff149f64625

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #2387: chore: use `scverse-misc`'

4. Push to a named branch:

git push YOURFORK 0.12.x:auto-backport-of-pr-2387-on-0.12.x

5. Create a PR against branch 0.12.x, I would have named this PR:

"Backport PR #2387 on branch 0.12.x (chore: use scverse-misc)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.