Message398899
The conflict comes from the fact that the documentation is written from the perspective of the procedure-oriented interface
"All methods of TurtleScreen/Screen also exist as functions, i.e. as part of the procedure-oriented interface"
The conflict in the documentation comes from the fact that there is a conflict in the code as-well. The way the conflict is resolved in the code is that:
"This TurtleScreen method is available as a global function only under the name clearscreen. The global function clear is a different one derived from the Turtle method clear."
I propose that we noindex the TurtleScreen.clear() method, and index the Turtle.clear() method instead which more accurately reflects the behaviour of the turtle module itself. A link to the TurtleScreen.clear() method will still be available through its alias TurtleScreen.clearscreen(). |
|
Date |
User |
Action |
Args |
2021-08-04 14:24:11 | Harry-Lees | set | recipients:
+ Harry-Lees, docs@python, ray_giraffe |
2021-08-04 14:24:11 | Harry-Lees | set | messageid: <1628087051.73.0.325247156457.issue44760@roundup.psfhosted.org> |
2021-08-04 14:24:11 | Harry-Lees | link | issue44760 messages |
2021-08-04 14:24:11 | Harry-Lees | create | |
|