Thank you for doing this. It should be possible to run tox as Udi suggested and create a PR for review purposes similar to the release process (see: https://beam.apache.org/contribute/release-guide/#build-the-pydoc-api-reference )
/cc +Valentyn Tymofieiev <[email protected]> -- This is likely a required item before retiring python 2 support. Ahmet On Mon, Oct 28, 2019 at 11:21 AM Udi Meiri <[email protected]> wrote: > I believe that generating pydoc for the website is still a manual process > (unlike the rest of the website?). > The reviewer will need to manually generate the docs (checkout the PR, run > tox -e docs). > > On Mon, Oct 28, 2019 at 10:55 AM Yoshiki Obata <[email protected]> > wrote: > >> Hi all. >> >> I'm working on enabling to generate Python SDK docs with Python3 [1] >> I have modified scripts and now reviewing generated docs in someone’s >> eyes is needed. >> >> But there seems to be no existing way to upload generated docs to >> where anyone can access unlike website html which can be uploaded to >> GCS via Jenkins job. >> Would anyone know good way to make generated docs accessible for >> anyone for convenience of reviewing them? >> >> [1] https://issues.apache.org/jira/browse/BEAM-7847 >> >> >> Best regards, >> Yoshiki >> >> >> -- >> Yoshiki Obata >> mail: [email protected] >> gh: https://github.com/lazylynx >> >
