python / python/cpython

Restructure the `turtle` documentation

Ouverte
#157,847 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@StanFromIreland y travaille déjà.

Depuis le 20/9/2026.

docs
Langage dominant
Python
Étoiles
77.2k
Forks
36k
Métriques de merge des PR
Métriques de PR en attente

Description

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
  • gh-157868

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.