Poliastro: `py:mod` roles do not link to corresponding summary page

[astrojuanlu]

And they have never worked, apparently. See for example https://docs.poliastro.space/en/v0.13.1/changelog.html#backwards-incompatible-changes

I wonder if this is a limitation of autodoc or if we're misusing it.

[DhruvSondhi]

Hello @astrojuanlu, I did some digging around ... Though I haven't found any example where I can see the actual working of this py:mod tag, I have made some changes as shown

I don't understand this but this looks better :) ... It doesn't link to the summary page though 😥

[astrojuanlu]

It doesn't link to the summary page though 😥

Then it's not what we want... If py:class and py:meth work, I would be very interested in knowing why py:mod doesn't.

[DhruvSondhi]

It would be very interested in knowing why py:mod doesn't

I may have understood why it is not working ... It is not working because the current file is not present in the updated codebase ... what I mean by this is that when we are referencing the module with the py:mod directive, due to the newer codebase not having the file, it is not linking it ... similar case would be when we link to a function or a class which doesn't exist in the codebase 🤔 ... Also because of this we are not able to link to the module page in the newer revision of the docs via the codebase

[astrojuanlu]

You're right that the example I linked is a bad one. But I tried with other modules that do exist, with identical result.

[DhruvSondhi]

@astrojuanlu I found the answer, we were looking for ... it is on their docs page 🤦🏼

We can do nothing in this context ... I think this closes this issue as well 😞 {Link here as well, check the last line of the paragraph}

[astrojuanlu]

Hahaha oh dear, I didn't know this! Thanks for actually _reading the docs_... I think it's safe to close this issue then.