Before:

After:

👍

Related question unrelated to Astropy--I was trying to include an inheritance diagram for a different project in its docs. But I couldn't figure out how to say, given a class, generate an inheritance diagram including this class and all its subclasses. Any ideas? Would one of these plugins help?

By the by, if this is merged don't let me forget to also merge it into astropy-helpers.

The inheritance-diagram mostly works the other way: given a class, diagram its base classes. (Or, as we use it in astropy, give it a module and diagram everything in it). To do what you want, I think you'd probably have to subclass it the inheritance-diagram directive. It shouldn't be too bad, because it already takes as input a "set of classes" -- you'd just need a shim to generate that set and pass it along.

This looks great! Will review today.

cc @kbarbary @eteq since it fixes all the API link-related issues!

@mdboom - this looks good to me! Is it ready to merge?

@mdboom - this is a tricky way to solve this, but it's nice, and I like the result!

The one concern is that this may have unintended consequences when there's name overlap. E.g., if in the future someone adds a warning to astropy.time called IllegalSecondWarning, this will cause the links to resolve incorrectly, right?

This was still fine right now, because it's better than the alternative of not merging, but I want to make sure I understand this in case it ends up happening down the road.