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 chris.jerdonek
Recipients chris.jerdonek, docs@python, r.david.murray
Date 2012-08-16.16:18:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I think we generally upgrade it exactly when there is a new Sphinx feature we want for our docs :)

:)  Would the appropriate way to handle it be then to create an issue to "upgrade Sphinx when XXX issue is resolved" and link to the corresponding Sphinx issue?

I also see value in Python being able to track and possibly assist Sphinx in fixing an issue that we want.

Incidentally, issue 15455 may fall into the same category now that I know more.
Date User Action Args
2012-08-16 16:18:49chris.jerdoneksetrecipients: + chris.jerdonek, r.david.murray, docs@python
2012-08-16 16:18:49chris.jerdoneksetmessageid: <>
2012-08-16 16:18:48chris.jerdoneklinkissue15693 messages
2012-08-16 16:18:48chris.jerdonekcreate