From d012a66ed6bf9e8bcc1157144f7755882c926e87 Mon Sep 17 00:00:00 2001 From: Andrew Janke Date: Mon, 17 Dec 2018 14:25:42 -0500 Subject: [PATCH] Use "local" instead of "global" to describe where imports go --- docs/writing/structure.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/writing/structure.rst b/docs/writing/structure.rst index 663605fb0..9160a04d4 100644 --- a/docs/writing/structure.rst +++ b/docs/writing/structure.rst @@ -441,8 +441,8 @@ bad practice. **Using** ``import *`` **makes code harder to read and makes dependencies less compartmentalized**. Using ``from modu import func`` is a way to pinpoint the function you want to -import and put it in the global namespace. While much less harmful than ``import -*`` because it shows explicitly what is imported in the global namespace, its +import and put it in the local namespace. While much less harmful than ``import +*`` because it shows explicitly what is imported in the local namespace, its only advantage over a simpler ``import modu`` is that it will save a little typing.