[issue30327] Version may be out of date in travis.yml

Changes by Brett Cannon : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue30327] Version may be out of date in travis.yml

Brett Cannon added the comment: I agree with Victor since that's why I set up the Travis file that way. :) Thanks to this issue, though, I have added a comment to .travis.yml to explain why the version is what it is. -- ___ Python tracker

[issue30327] Version may be out of date in travis.yml

Changes by Brett Cannon : -- pull_requests: +1648 ___ Python tracker ___ ___

[issue30327] Version may be out of date in travis.yml

STINNER Victor added the comment: @Brett: What do you think? -- nosy: +brett.cannon ___ Python tracker ___

[issue30327] Version may be out of date in travis.yml

STINNER Victor added the comment: Python 3.6 is the latest stable release of Python. It's perfectly fine to *build the documentation* using that version. I don't think that the Travis "docs job" must test that Sphinx works on the nightly version: this work should be done by Sphinx, not by the

[issue30327] Version may be out of date in travis.yml

Changes by Roundup Robot : -- pull_requests: +1625 ___ Python tracker ___

[issue30327] Version may be out of date in travis.yml

New submission from Jensen Taylor: It's only 3.6. I may be talking nonsense but it didn't quite look right -- components: Build, Tests messages: 293381 nosy: Jensen Taylor priority: normal severity: normal status: open title: Version may be out of date in travis.yml type: behavior