[issue22571] Remove import * recommendations and examples in doc?

Terry J. Reedy added the comment: I am going to accept Raymond's rejection of a general change. I will reconsider the tkinter doc should I ever work on it. For IDLE code, I have settled on 'from tkinter import Tk, Text, ..., perhaps followed by 'from tkinter.ttk import Scrollbar, ...'. But

[issue22571] Remove import * recommendations and examples in doc?

Carol Willing added the comment: Hi @terry.reedy @rhettinger, I'm triaging the 'turtle' open issues. I'm wondering if we can close this issue with a resolution of "Remind". If there are '*' imports that folks feel strongly about changing, then those could be opened now or in the future as a

[issue22571] Remove import * recommendations and examples in doc?

Raymond Hettinger added the comment: Many of these (such as collections, collections.abc, decimal, and itertools) use import * as part of the doctest setup and are not part of the generated page shown to users. Also, I don't think you should be aggressive about removing the other example that

[issue22571] Remove import * recommendations and examples in doc?

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue22571] Remove import * recommendations and examples in doc?

Mark Dickinson added the comment: I think it's fine to recommend using (for example) `>>> from decimal import *` at the command-line prompt when experimenting with a module. It's a quick way to get yourself into a state where you can easily experiment with that module and its features. That'

[issue22571] Remove import * recommendations and examples in doc?

New submission from Terry J. Reedy: PEP 8 recommends against 'from mod import *' because it makes reading harder and is bad for code analysis. My experience with retrofitting tests to idlelib modules with tkinter * imports is that it also makes testing harder since the testing strategy depend