P. L. Lim

I don't maintain this package, so I am not qualified to review. Sorry and good luck!

> Since some of spherical_geometry is written in C, it doesn't seem to address that need But does it *have* to be in C?

If this is re-milestone to v7.0 or later, please use the new `perf` change log category if applicable, see: * https://github.com/astropy/astropy/pull/16694

You should have rebased and run CI one more time. I think merging this broke CI on main. https://github.com/astropy/astropy/actions/runs/16295647880

Re: show_as_datagrid The pro is we are free of API debt. The con is people might not discover it, though I guess we can add that as the alternative in...

Hmm. I'd rather not have the burden of us keeping track of ipydatagrid changes, especially since they don't seem to have proper API documentation.

> make this mechanism extendible What kind of mechanism do you have in mind?

Re: https://github.com/astropy/astropy/pull/17165#issuecomment-2408914153 @taldcroft , but then how do we document all the different combos of `kwargs` per backend?

Also multiple backends are going to bloat up our "optional" dependencies.

So... you all want to get rid of notebook support altogether a few months ago. But now want to support all whole slew of backends? That is quite a turn.