[issue1513695] new turtle module
report at bugs.python.org
Tue Jun 3 00:55:15 CEST 2008
Gregor Lingl <gregorlingl at users.sourceforge.net> added the comment:
In my last posting i forgot a fourth proposition.
Currently one has the Turtle.methods fill(), begin_fill() and end_fill()
As is stated in the old turtle docs the specification of fill is "rather
complex". begin_fill() and end_fill(), are identical to fill(True) and
fill(False) (or fill(1) and fill(0)). That means, that begin_fill()
sometimes may do somthing unexpected, namely complete som filling
underway. In the new turtle module fill() without arguments returns the
filling state, i. e. True/False respectively.
I'd prefer the following:
begin_fill() should only start a new filling process and cancel some
underway, if necessary (that means: a filling without end_fill will
not take place)
end_fill() should only complete the current filling process
a new method filling() should be used to ask if same filling is
currently taking place
and fill() could be dropped. (deprecated in 2.6)
I think Vern Ceders intention with introducing begin_fill and end_fill
was to have a clear and easily understandable meaning, which is only
partially accomplished with the current solution.
What is your opinion?
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list