This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients docs@python, ethan.furman, mark, terry.reedy
Date 2014-08-02.21:24:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407014658.78.0.149149384652.issue22122@psf.upfronthosting.co.za>
In-reply-to
Content
I think your suggestion is wrong as is and that this issue should be revised or closed.  The simple initial example is a complete program. PEP8 discourages 'import *' but it is acceptable in this context. The snippets you refer to follow

"24.1.3. Methods of RawTurtle/Turtle and corresponding functions

Most of the examples in this section refer to a Turtle instance called turtle."

Methods are always documented as method calls, and they should be here too. The function interface can only be used for 1 turtle, while drawings often require more than 1.  See turtledemo for examples such as 'forest', which uses 3 Turtle instances.

Nothing says that users have to name an instance 'turtle'.  In practice one might use 't1', 't2', etc, or other short names.  Within a subclass of Turtle, with added methods, the prefix would be 'self.'. The quote above could be, and perhaps should be augmented with a reminder that "If one uses the function interface for one turtle or the first of many turtles, 'turtle.' should be omitted."  As a further concession to beginners, this could even be follows by "If one uses the object interface, replace 'turtle' with the actual name of a particular turtle."
History
Date User Action Args
2014-08-02 21:24:18terry.reedysetrecipients: + terry.reedy, mark, docs@python, ethan.furman
2014-08-02 21:24:18terry.reedysetmessageid: <1407014658.78.0.149149384652.issue22122@psf.upfronthosting.co.za>
2014-08-02 21:24:18terry.reedylinkissue22122 messages
2014-08-02 21:24:18terry.reedycreate