Removing pre-built PDF documentation from docs.python.org

[AA-Turner]

Documentation

Following https://discuss.python.org/t/101343/45

Linked PRs

• gh-139436: Remove link to the PDF downloads #139142
• [3.14] gh-139436: Remove link to the PDF downloads (GH-139142) #139426
• [3.13] gh-139436: Remove link to the PDF downloads (GH-139142) #139427
• [3.12] gh-139436: Remove link to the PDF downloads (GH-139142) #139428
• [3.11] gh-139436: Remove link to the PDF downloads (GH-139142) #139430
• [3.10] gh-139436: Remove link to the PDF downloads (GH-139142) #139431
• gh-139436: Remove dist-pdf from the docsbuild-scripts rebuild target #139437
• [3.14] gh-139436: Remove dist-pdf from the docs archives rebuild target (GH-139437) #139692
• [3.13] gh-139436: Remove dist-pdf from the docs archives rebuild target (GH-139437) #139693
• [3.12] gh-139436: Remove dist-pdf from the docs archives rebuild target (GH-139437) #139694
• [3.10] gh-139436: Remove dist-pdf from the docs archives rebuild target (GH-139437) #140412
• [3.9] gh-139436: Remove dist-pdf from the docs archives rebuild target (GH-139437) #140413
• GH-139436: Remove references to downloadable PDF documentation #140416
• GH-139436: Remove PDF and CHM from IDLE HelpSource #140418
• [3.14] GH-139436: Remove references to downloadable PDF documentation (GH-140416) #140419
• [3.13] GH-139436: Remove references to downloadable PDF documentation (GH-140416) #140420
• [3.11] gh-139436: Remove dist-pdf from the docs archives rebuild target (#139437) #141164
• [3.13] GH-139436: Remove PDF and CHM from IDLE HelpSource (GH-140418) #142551
• [3.14] GH-139436: Remove PDF and CHM from IDLE HelpSource (GH-140418) #142552

[adorilson]

Are there instructions on how to create the PDF documentation? I didn't find it.

[AA-Turner]

I added instructions to the download page: https://docs.python.org/dev/download.html

You may need to force-refresh.

A

[adorilson]

I added instructions to the download page: https://docs.python.org/dev/download.html

You may need to force-refresh.

A

Thank you.

Have you thought about translations? Could the teams change the string to include something like "for xx_XX language access the team's page for..." I believe each translation team could provide these PDF files.

[StanFromIreland]

change the string to include something like "for xx_XX language

For reference, per PEP 545, this must be done for bugs.po (although it is not always followed), it would be useful to have a better way and standardised way to do this, e.g. .. only:: translation (I proposed such in #137449).

Also, I propose adding a note in the devguide that explains how to build a translation (see python/devguide#1660), since this is not covered actually.

[ambv]

DPO = discuss.python.org. Let's don't confuse it by calling docs "d.p.o." as well.

[AA-Turner]

Au contraire, d.p.o = docs.python.org :)

That said, no objection to disambiguating the title!

A