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 kirill_simonov
Recipients kirill_simonov
Date 2008-09-16.21:05:36
SpamBayes Score 1.9466609e-07
Marked as misclassified No
Message-id <1221599171.66.0.226018210692.issue3884@psf.upfronthosting.co.za>
In-reply-to
Content
I wonder why the module 'turtle' was moved to the 'tkinter' package.  It
is not a part of Tk, it does not provide new or extend existing tkinter
API.  While it uses tkinter, so do pydoc or idle; this is just an
implementation detail.  If some day a new GUI library replaces tkinter
in the standard Python library, turtle's interface will not have to be
changed, only the implementation.  Moreover this change unnecessarily
breaks all existing demos and tutorials that use turtle.  Why do this if
it does not give any substantial benefits?  Finally, 'import turtle' is
easier than 'from tkinter import turtle' for complete newbies in
programming, who are the primary users of this module.

So I propose to keep turtle a top-level module as it was in Python 1 and 2.
History
Date User Action Args
2008-09-16 21:06:11kirill_simonovsetrecipients: + kirill_simonov
2008-09-16 21:06:11kirill_simonovsetmessageid: <1221599171.66.0.226018210692.issue3884@psf.upfronthosting.co.za>
2008-09-16 21:05:37kirill_simonovlinkissue3884 messages
2008-09-16 21:05:36kirill_simonovcreate