# Where should the Argument Clinic docs live?

**URL:** <https://discuss.python.org/t/where-should-the-argument-clinic-docs-live/30160>\
**Category:** Documentation\
**Tags:** argument-clinic, diátaxis\
**Created:** [July 24, 2023, 12:35am UTC](https://discuss.python.org/t/where-should-the-argument-clinic-docs-live/30160 "2023-07-24T00:35:46Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![CAM-Gerlach](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/cam-gerlach/32/3688_2.png) [@CAM-Gerlach](https://discuss.python.org/u/CAM-Gerlach)\
**Post date:** [July 25, 2023, 3:57pm UTC](https://discuss.python.org/t/where-should-the-argument-clinic-docs-live/30160/9 "2023-07-25T15:57:39Z")

</div>

Just to comment on this point—

> [@erlendaasland](#):
>
> easier to add links to other parts of the Python Docs, like stdlib modules and CPython source files.

Actually, since the CPython docs is included as an intersphinx mapping in the devguide, its exactly as easy to link/cross-reference CPython docs targets in the devguide as in the CPython docs, as all the same syntax will work transparently.

Additionally, in the devguide cross-reference different specific versions of the CPython docs by adding them as separate intersphinx mappings (like we do in the PEPs), e.g. you can have a xref that always points to the latest dev version, the latest stable version, or a specific feature release.

And cross-referencing source files is as easy or easier thanks to the `:cpy-file:` role Ezio added to the devguide.

---

_[View the full topic](https://discuss.python.org/t/where-should-the-argument-clinic-docs-live/30160)._