Gregor Lingl <[EMAIL PROTECTED]> added the comment: > Most definitely. The module went into Python without any review > whatsoever. Nobody (but you) has ever looked at the code in detail.
That's not True! Brad Miller, for example, who also had submitted patches to the pythontracker, coauthor of "Python Programming in Context", has used a predecessor of turtle.py as a main tool (swiss army knife, as he says) in his book. He has contributed a few patches (via private communication, before the module went into the Python trunk), one of them directly concerning the update method. He had also suggested some of the features, which I have added towards the end of the development. > You might argue that with due process, review should have taken > place before the code was integrated. You might be right, but then > the new turtle module wouldn't have been part of Python 2.6. Rigth, more or less. At least I had expected, that someone reads the doc-strings of the approx. 15 classes in the module. The one of TurtleScreenBase reads like this: """Provide the basic graphics functionality. Interface between Tkinter and turtle.py. To port turtle.py to some different graphics toolkit a corresponding TurtleScreenBase class has to be implemented. """ Gregor _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4117> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
