Skip to content

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

Description

@AA-Turner

Documentation

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

Linked PRs

Activity

  1. adorilson commented on Sep 30, 2025

    @adorilson
    Contributor

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

  2. AA-Turner commented on Sep 30, 2025

    @AA-Turner
    MemberAuthor

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

    You may need to force-refresh.

    A

  3. adorilson commented on Oct 1, 2025

    @adorilson
    Contributor

    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.

  4. StanFromIreland commented on Oct 1, 2025

    @StanFromIreland
    Member

    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.

  5. added a commit that references this issue on Oct 7, 2025
  6. added a commit that references this issue on Oct 7, 2025
  7. changed the title [-]Removing pre-built PDF documentation from d.p.o[/-] [+]Removing pre-built PDF documentation from docs.python.org[/+] on Oct 7, 2025
  8. ambv commented on Oct 7, 2025

    @ambv
    Contributor

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

  9. AA-Turner commented on Oct 7, 2025

    @AA-Turner
    MemberAuthor

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

    That said, no objection to disambiguating the title!

    A

  10. added a commit that references this issue on Oct 7, 2025
  11. added 2 commits that reference this issue on Oct 7, 2025
  12. 7 remaining items

  13. added 2 commits that reference this issue on Oct 21, 2025
  14. added 2 commits that reference this issue on Oct 21, 2025
  15. added 2 commits that reference this issue on Oct 31, 2025
  16. added a commit that references this issue on Nov 6, 2025
  17. added a commit that references this issue on Dec 6, 2025
  18. added a commit that references this issue on Dec 9, 2025
  19. added 2 commits that reference this issue on Dec 11, 2025
  20. added 2 commits that reference this issue on Dec 11, 2025
  21. added a commit that references this issue on Dec 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation in the Doc dir

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions