👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

My instigation, because I asked about https://github.com/astropy/sphinx-astropy/pull/40/files#r624715168

Does this lead to any weird circular dependency issues?

😄

Hmm. This step appears to be a bit trickier. There's some intersphinx subtleties since the intersphinx_mapping in sphinx_astropy.sphinx refers to astropy, but this is astropy stable, and we want the intersphinx to refer to the version being built.

@pllim @embray , git blame says y'all last modified the line

del intersphinx_mapping['astropy']  # noqa: F405

Any suggestions how to intersphinx to the version being built? Is that even possible? Larger question, is this even a good idea, or should we just keep the physical type xref explicitly in Astropy/docs/conf.py (in addition to in sphinx_astropy v1 for affiliate packages)?

Edit : astropy/sphinx-astropy#15 is relevant.

Any suggestions how to intersphinx to the version being built?

Maybe #11622 is what you need?

p.s. We don't really have enough resources for big changes to sphinx-astropy.

Maybe #11622 is what you need?

Looks like it. It helped me figure out the solution. Thanks!

p.s. We don't really have enough resources for big changes to sphinx-astropy.

Understood. I'm working with @adrn to enable some of the numpydoc xref to be easily used by affiliate packages. I'm trying to avoid messing with any intersphinx magic, just moving some dictionaries around. Probably nothing big.

@adrn @mhvk. This works! We can move much of the numpydoc xref stuff from Astropy to sphinx-astropy, thereby allowing affiliate packages to use the xref. I've set it up so that sphinx-astropy creates affiliate links, so here in astropy we just strip the intersphinx parts from the links with two quick .replace() string operations.

There are two things before I undraft:

1. How much should be moved to sphinx-astropy?
2. The sphinx-astropy PR needs to be merged first (intersphinx xref sphinx-astropy#40)

I think #11690 can be lightly modified (once merged) to skip the need for the intersphinx stripping happening in this PR. That would make astropy_sphinx "just" work for both affiliate and astropy.

@nstarman - this looks nice, but obviously still needs the astropy-sphinx PR to be merged first...

astropy-sphinx PR to be merged first

Unfortunately, a new release... No chance that sphinx-astropy could release in lock-step with Astropy (if there's a change in sphinx-astropy) ?

chance that sphinx-astropy could release in lock-step with Astropy

Right now, release is done as needed and when people have time. I won't have time this week.

Request review: @pllim @saimn @astrofrog @adrn @mhvk

@mhvk @adrn. Failures unrelated?

32-bit/parallel failure is due to #11878 .

I am not sure if I can review this PR. I have not been following the doc stuff closely.

32-bit/parallel failure is due to #11878 .

Thanks! I was worried there.

I am not sure if I can review this PR.

NP. I tagged because of astropy/sphinx-astropy#40.

I think this is just ready to go in, as it was a logical follow-up of the sphinx astropy update. But maybe leave open for a day in case others want to have a look.

reminder to self: really need to do #11584 to also document which x-refs are in sphinx-astropy, how an affiliate package should use all this (also add documentation in sphinx-astropy), and how to add a term to sphinx-astropy and remove in astropy (if present).

Thanks @nstarman !