-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Review bpo-21956: Doc files deleted from repo are not deleted from docs.python.org. #41
Comments
Thanks. The issue seems to be resolved and presumably can be closed, as it seems in the intervening 8 years the adoption of the modern Sphinx rendering system and the hosting backend have resulted in documentation being appropriately deleted when it no longer exists in the source, as the link doc no longer exists and gives a 404, even for Python 3.4. |
Hm, was there a change to the hosting backend? I know nothing about these things. |
It happened in February with 3.11 due to a PDF build failure and some caching problems: And earlier in 2017, fixed by changing a Ping also @JulienPalard. |
Yes as mentionned by @hugovk it's fixed since 2017 but it could still happen in very unfortunate conditions. To be very precise:
If python/psf-salt#226 gets done, or if any experience using html-only builds are done, AND a crash happen during the PDF build, it would result in the following situation:
(Old files are not deleted by html-only builds because it would delete PDFs...) Hopefully build errors are monitored using Sentry, I don't know who receive the notifications though, I know I receive them and I bet Ee receives them. |
Ah, OK. I think it's fine if an emergency workaround build system keeps deleted files, as long as regular builds are fine. Thanks for confirming! |
An old open issue that you may be able to resolve.
The text was updated successfully, but these errors were encountered: