Message 298461 - Python tracker

➜

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	ned.deily
Recipients	brett.cannon, docs@python, larry, ned.deily
Date	2017-07-17.05:55:01
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1500270901.55.0.428336159058.issue30939@psf.upfronthosting.co.za>
In-reply-to

Content
> I wonder if we should pin sphinx directly instead of the approximate pin we > have now to prevent this sort of thing in the future? Perhaps. OTOH, we will find out about Sphinx incompatibilities pretty quickly that way, rather than having doc builds potentially silently fail or only finding out about the problem at release time.

> I wonder if we should pin sphinx directly instead of the approximate pin we
> have now to prevent this sort of thing in the future?

Perhaps. OTOH, we will find out about Sphinx incompatibilities pretty quickly that way, rather than having doc builds potentially silently fail or only finding out about the problem at release time.

History
Date	User	Action	Args
2017-07-17 05:55:01	ned.deily	set	recipients: + ned.deily, brett.cannon, larry, docs@python
2017-07-17 05:55:01	ned.deily	set	messageid: <1500270901.55.0.428336159058.issue30939@psf.upfronthosting.co.za>
2017-07-17 05:55:01	ned.deily	link	issue30939 messages
2017-07-17 05:55:01	ned.deily	create