On Sun, Dec 31, 2017 at 8:03 PM, Abdur-Rahmaan Janhangeer <arj.pyt...@gmail.com> wrote: > @Chris > > hum nice point > > it seems to be related to namespace convenience > > like > > 1 from x import * > > is likelier to cause conflicts than > > 2 import x
This is correct. Also, when you read the code, you can instantly tell that "x.ALL" is not the same as the built-in "all" function, but it's less obvious if they're both just simple names. Some modules are designed to be star-imported (tkinter being one of them), but even there - and *definitely* for other modules - it's much clearer to use module imports. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
