Re:Say “no” to import side‐effects in Python
by ta0967 on Saturday April 05, 2014 @03:47PM
(#7538194)
Whether they import a module or not is - IMO - irrelevant. I was responding to this claim: In Python, side-effects are simply not acceptable at all. One should instead put the code with the side-effect in a function and call it. `__future__` imports are obviously and purposefully side-effectful, there's no `print_function()`.
[ Parent
| on HN ]
There are no comments on this comment yet.