Hi Dave,
I would be interested in your two round build script if you wish to share
it :-)
I have about 30 some repos across 3 organizations that would really benefit
from any tips/tools that simplifies linking between them on RTD.
Thanks,
Carol
On Sunday, April 10, 2016 at 5:44:48 PM UTC-7,
I wanted to bump this question back up. Has anyone else come up with a
good way to handle arbitrary intersphinx links between docs that are
to be hosted on readthedocs? Forcing a "no circular links" policy
imposes significant restrictions on structuring multiple Git repos
that are related. My solut
Thanks, this is a way to do it, though it will be expensive in time.
Thanks for the feedback, at least I know I haven't overlooked something
that's available.
--Ned.
On Friday, January 22, 2016 at 5:59:31 PM UTC-5, Daniel Beck wrote:
>
> Hi Ned,
>
> I've had this problem myself. If you build a
Hi Ned,
I've had this problem myself. If you build a given Sphinx project pointing
to a not yet built .inv file (or files), Sphinx will issue a bunch of
warnings (e.g., `WARNING: intersphinx inventory
'../path_to_other_project/objects.inv' not fetchable` ) but Sphinx will
build the project's own .
I solved this for me by organizing my projects so that their docs don't
refer to each other in a circular way, and by organizing my builds so
that the order of dependency is respected:
a (top-level, no intersphinx refs)
b can refer to a
c can refer to b and a
Luc
On 22/01/16 19:30, Ned Batchelde
At edX, we're using intersphinx to link among our own projects. But it's
designed to pull .inv files from readthedocs. This means if we add a new
reference between projects, the build will fail until the target has been
published. I tried using the second value in the mapping tuple to point t
