Author ned.deily
Recipients Maciej Olko, docs@python, eric.araujo, ezio.melotti, mdk, ned.deily, python-dev, rhettinger, serhiy.storchaka, vstinner, willingc, xtreak
Date 2020-04-10.00:48:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586479685.17.0.52495404871.issue40204@roundup.psfhosted.org>
In-reply-to
Content
I agree that it should be easier to keep them all in sync.  But my point is that the on-going official doc builds (some multi[ple times per day) for all of the active versions (2.7 and 3.6 through 3.9) are using 2.3.1 so we should be doing CI against that version as well.  The docs builds are configured in https://github.com/python/docsbuild-scripts.  So whenever requirements.in is update there, the CI versions should be updated as well. Even better would be someway to auto sync them.

Julien, any ideas on this?
History
Date User Action Args
2020-04-10 00:48:05ned.deilysetrecipients: + ned.deily, rhettinger, vstinner, ezio.melotti, eric.araujo, docs@python, python-dev, serhiy.storchaka, willingc, mdk, xtreak, Maciej Olko
2020-04-10 00:48:05ned.deilysetmessageid: <1586479685.17.0.52495404871.issue40204@roundup.psfhosted.org>
2020-04-10 00:48:05ned.deilylinkissue40204 messages
2020-04-10 00:48:04ned.deilycreate