-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: PythonDocs fail to build after moving to Python3.9 #32728
Comments
This prevents generating site PR for Beam 2.60.0RC1. For now I am downgrading workflow python version to 3.8, but still need to be fixed by the next release cc: @jrmccluskey |
after moving back to Python3.8, Build failing https://github.com/apache/beam/actions/runs/11266727364/job/31330701433 due to some commit originally should fail pydoc test slipped in |
I am trying to downgrade the PreCommit PythonDocs to run with Python 3.8, find error: https://github.com/apache/beam/actions/runs/11267199804/job/31331924456 |
Should hopefully just be a sphinx version upgrade, let me see how intensive that is |
For reference, we pin sphinx<=2.0, the latest sphinx release is 8.0.2. The last release supporting Python 3.9 is 7.4.7, so the goal is to catch us up to speed there |
Okay https://github.com/apache/beam/actions/runs/11276977276/job/31362056928 should pass with modernized dependencies. The biggest issue is that the original pydoc script will fail if there are any warnings generated, not just errors, and I don't know if it's particularly worth it to try and plug all of those holes while this is a release blocker. Assuming I don't find other issues in subsequent runs, I can open a PR to get these changes into master |
Thanks, that sounds good |
What happened?
https://github.com/apache/beam/actions/workflows/beam_PreCommit_PythonDocs.yml is actually failing:
However, looks like our build target does not check return code, and the task as well as GHA workflow always pass
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components
The text was updated successfully, but these errors were encountered: