We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to reproduce:
Expected result:
Actual result:
The text was updated successfully, but these errors were encountered:
I would like to work on this issue, but i cant seem to find the file in docs, if you would guide, that would be helpful
Sorry, something went wrong.
hey @AlexeyKuzko i wanted to work on this issue if anybody is not assigned , could u please help me regarding where do i start from ?
The issue is that the 3.9 docs at https://docs.python.org/3.9/ are for 3.9.17 (the footer says when the docs were built: "Last updated on Jul 04, 2023"), but 3.9.18 is the newest version (released 2023-08-24).
Similarly, https://docs.python.org/3.8/ is 3.8.17, built on Jul 05, 2023, but 3.8.18 is the newest (2023-08-24).
In both cases, there are docs changes (committed 2023-08-22) for those two security releases:
https://github.com/python/cpython/commits/3.9/Doc https://github.com/python/cpython/commits/3.8/Doc
@JulienPalard What do we need to do for new 3.9 and 3.8 docs builds? Can you trigger them manually?
(/3.10 is okay and has the latest 3.10.13)
/3.10
No branches or pull requests
Documentation
Steps to reproduce:
Expected result:
Actual result:
The text was updated successfully, but these errors were encountered: