python / python/cpython

Restructure the `turtle` documentation

Offen
#157,847 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@StanFromIreland arbeitet bereits daran.

Seit 20.9.2026.

docs
Vorherrschende Sprache
Python
Sterne
77.2k
Forks
36k
PR-Merge-Kennzahlen
PR-Kennzahlen ausstehend

Beschreibung

Documentation

Currently, it's a little messy. We have obsolete sections (https://github.com/python/cpython/pull/157846) and several that seem to duplicate each other. Inspired by https://github.com/python/cpython/issues/94635, I will restructure the documentation remove the duplicated content, and to have a clearer order and table of contents than what we have now. A rough plan:

turtle --- Turtle graphics
  (intro prose, merges "Introduction" and "Get started",
   keep the sidebar image, then optional-module include plus the Tk
   note from the how-to, then a "This document includes four main
   sections:" like in sqlite3 documentation)

Tutorial
  Starting a turtle environment
  Basic drawing
  Making algorithmic patterns
  etc.

Reference
  Turtle methods and functions             (current "Methods of RawTurtle/Turtle...")
  Screen methods and functions             (current "Methods of TurtleScreen/Screen...")
  Classes                                  (current "Public classes")
  Exceptions

How-to guides
  How to automatically begin and end filling
  How to use the turtle module namespace
  How to use turtle graphics in a script
  How to use object-oriented turtle graphics
  How to use help                          (moved from "Help and configuration")
  How to configure Screen and Turtles      (moved from "Help and configuration")

Explanation
  The object-oriented interface            (current "Explanation")

turtledemo --- Demo scripts                (unchanged)
Linked PRs
  • gh-157846
  • gh-157849
  • gh-157850
  • gh-157851
  • gh-157854

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.