On Tuesday, April 11, 2017 4:11:44 PM EDT Brett Cannon wrote:
> One place where this might actually show itself to be useful is with
> the PEPs. That build toolchain generates HTML files directly and
> doesn't even use Sphinx (at least not yet). I have opened
> https://github.com/python/peps/issues/241 to discuss the idea.
Sounds like a good place to try the process.
> > One of the reasons why we went with GH Pages for asyncpg is that at
> > the time RTFD did not support Python 3.5 syntax and we wanted to
> > use autodoc. Could this be an issue when building Python
> > documentation? Can the master branch Docs/ be built by Sphinx
> > running on Python 3.4?
> There's no version requirement for the docs as we don't use the
> autodoc extension. And I think Read the Docs uses a newer image now
> as I was buliding the docs for gidgethub using autodoc and that uses
> 3.5 syntax.
>
> And how would versions be handles for GH Pages? E.g. how would
> docs.python.org handle viewing the e.g. 2.7 data? I guess you're just
> really careful to upload to subdirectories in the gh-pages branch?
Yes, we can continue using the current switcher and subfolders.
Elvis
_______________________________________________
core-workflow mailing list
core-workflow@python.org
https://mail.python.org/mailman/listinfo/core-workflow
This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct
