DOC: Only show developer docs in latest#11342
Conversation
19d788c to
39fa499
Compare
This comment has been minimized.
This comment has been minimized.
a06fbe5 to
4d3a33d
Compare
| Alternatively, if you intend to do development on other software that uses | ||
| ``astropy``, such as an affiliated package, consider installing ``astropy`` into a | ||
| :ref:`virtualenv<using-virtualenv>`. | ||
| ``astropy``, such as an affiliated package, consider installing ``astropy`` into a `virtualenv <https://docs.astropy.org/en/latest/development/workflow/virtualenv_detail.html>`__. |
There was a problem hiding this comment.
Note: This gives the exact rendered look, except the link when you hover over the text.
There was a problem hiding this comment.
This is fine to me for now, but it touches on another point I would like to improve in the docs, by including more details (such as how to use virtualenv) in the install docs. Having this link is maybe ok for now, since even with installation docs improvements there still might be a link like "see here for more details on virtualenv".
OTOH it might be good just to remove this link outright--as I have noted in #10508 this page is outdated and misleading.
There was a problem hiding this comment.
I see that you have followed up at #11367 . Thanks!
|
|
||
| {%else%} | ||
|
|
||
| The developer documentation contains instructions for how to contribute to |
|
|
||
| {%else%} | ||
|
|
||
| See the `latest documentation on how to test your installed version of astropy <https://docs.astropy.org/en/latest/install.html#testing-an-installed-astropy>`__. |
There was a problem hiding this comment.
We could also add an intersphinx target for developer docs. I'll try that out.
There was a problem hiding this comment.
I see you opened issue #11366 . 👍 It would be very nice if you can get it to work. 😸
|
|
||
| {%else%} | ||
|
|
||
| See the `latest documentation on how to run the tests in a source checkout of astropy <https://docs.astropy.org/en/latest/install.html#testing-a-source-code-build-of-astropy>`__. |
mhvk
left a comment
There was a problem hiding this comment.
Looks great! Some small organizational comments.
| warnings | ||
| utils/index | ||
|
|
||
| {% if is_development %} |
There was a problem hiding this comment.
I wonder if it makes sense to just move these two items to the developer documentation section?
|
|
||
| {% if is_development %} | ||
|
|
||
| The developer documentation contains instructions for how to contribute to |
There was a problem hiding this comment.
How about keeping this sentence which is the same outside of the if clause? Good to keep everything as much the same as possible.
| {%else%} | ||
|
|
||
| The developer documentation contains instructions for how to contribute to | ||
| Astropy or affiliated packages, as well as coding, documentation, and |
There was a problem hiding this comment.
Since we are removing the "install the developer version" above, how about adding here:
"...affiliated pacakges, install and test the development version, as well as ..."
DOC: Fix broken paragraph on render [ci skip]
0b937ab to
f747d13
Compare
|
Thanks for the review, @mhvk ! I believe I have addressed your comments. |
|
I don't think my approval is needed (nor do I know enough about this is done to provide meaningful feedback). I merely commented on the thread at some point in time. I've removed myself form the reviewers list. |
|
Thanks, everyone! |
|
Hopefully this can get into the next bug fix release, so it lands in stable, @eteq or @astrofrog . 😉 |
| logger.warning(msg) | ||
|
|
||
| # Generate the page from Jinja template | ||
| app.connect("source-read", rstjinja) |
There was a problem hiding this comment.
Nice, I didn't even realize it was possible to do this.
There was a problem hiding this comment.
Me neither. Thanks to @Cadair for letting me copy-paste from SunPy!
| {%else%} | ||
|
|
||
| To read the developer documentation, you will need to go to the | ||
| `latest developer version of the documentation <https://docs.astropy.org/en/latest/#developer-documentation>`__. |
There was a problem hiding this comment.
I wonder if it wouldn't make sense to move the entire developer docs TOC to its own page, perhaps with a bit of expansion. If you'd like, I can make a quick prototype of what I have in mind in a separate PR, or added to this one. I am planning to do some overhaul of the developer docs anyways so it would be a good opportunity to get my feet wet.
There was a problem hiding this comment.
This PR is already merged last week, so you would need to open a follow-up PR. 😉
There was a problem hiding this comment.
Oh, somehow I didn't realize this was already merged. Ok then, if you think it's a good idea I can make a follow-up.
There was a problem hiding this comment.
Yeah, feel free to PR. The dev docs definitely need some TLC.
DOC: Only show developer docs in latest
DOC: Only show developer docs in latest






Description
This pull request is to hide dev docs unless it is in
latestdoc. For this to take effect, probably needs backport.Stable view at #11344 .
Fixes #10443
Dev
https://astropy--11342.org.readthedocs.build/en/11342/install.html
Stable
From #11344
https://astropy--11344.org.readthedocs.build/en/11344/install.html