Re:Fixing the Python subprocess interface
by ulope on Monday January 30, 2012 @01:35PM
(#3529991)
Because it leads to namespace pollution and hard-to-track-down bugs.
It's especially bad in this case where adding an executable in the system can suddenly shadow any built-in name (e.g. imagine someone adds a "print" or "sys" executable).
Re:Fixing the Python subprocess interface
by gbog on Tuesday January 31, 2012 @08:14AM
(#3533063)
Refactoring is also made much harder with import * if you have cascading modules. I have a pylint hook forbidding these before committing to our hg repo
It's especially bad in this case where adding an executable in the system can suddenly shadow any built-in name (e.g. imagine someone adds a "print" or "sys" executable).