This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author techtonik
Recipients benjamin.peterson, docs@python, eric.araujo, georg.brandl, techtonik
Date 2010-06-20.16:40:16
SpamBayes Score 0.0390443
Marked as misclassified No
Message-id <1277052019.12.0.611651299287.issue8996@psf.upfronthosting.co.za>
In-reply-to
Content
`someref` would be more convenient than :func:`someref` but in case of namespace conflict (for example, as a result of documentation merge it both :func:`someref` and :class:`someref` can appear) - it would be necessary to go through all the links in both sources and update ambiguous references to point to the right type.

But perhaps the biggest problem would be to explain users what happens. Also in the case when you create new :class:`someref` and Sphinx detects conflict.
History
Date User Action Args
2010-06-20 16:40:19techtoniksetrecipients: + techtonik, georg.brandl, benjamin.peterson, eric.araujo, docs@python
2010-06-20 16:40:19techtoniksetmessageid: <1277052019.12.0.611651299287.issue8996@psf.upfronthosting.co.za>
2010-06-20 16:40:17techtoniklinkissue8996 messages
2010-06-20 16:40:17techtonikcreate