Harry <harry.l...@gmail.com> added the comment:
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(). ---------- nosy: +Harry-Lees _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44760> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
