New submission from Michael Foord <mich...@voidspace.org.uk>: There are a couple of minor changes I'd like to make to the tutorial.
Section 6.1 introduces the import * syntax without noting that it is bad practise. I'd like to add the following text: The import * form is generally considered to be bad practise as it makes it hard to tell where the names you use in your code come from, *and* you can accidentally overwrite names if you import something that is already defined elsewhere. It can still be useful when working in the console. Section 6.4.1 uses Windows 95 and DOS 8+3 as the reason that importing from packages doesn't automatically import all sub-packages. This is out of date and not the most compelling reasoning anyway. I'd like to replace that text with: Perhaps this should go out to the filesystem, find which submodules are present in the package, and import them all. This could take a long time and importing sub-modules might have unwanted side-effects that should only happen when the sub-module is explicitly imported. ---------- assignee: michael.foord components: Documentation keywords: easy messages: 92324 nosy: michael.foord severity: normal status: open title: Tutorial changes versions: Python 2.7, Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6849> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
