kennethreitz/python-guide
1
0
Fork 0
mirror of https://github.com/kennethreitz/python-guide.git synced 2026-06-05 06:46:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Use "local" instead of "global" to describe where imports go

Browse Source
This commit is contained in:
Andrew Janke
2018-12-17 14:25:42 -05:00
parent cafe323e0e
commit d012a66ed6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/writing/structure.rst
+2 -2
View File
@@ -441,8 +441,8 @@ bad practice. **Using** ``import *`` **makes code harder to read and makes
dependencies less compartmentalized**. dependencies less compartmentalized**.
Using ``from modu import func`` is a way to pinpoint the function you want to 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 import and put it in the local namespace. While much less harmful than ``import
*`` because it shows explicitly what is imported in the global namespace, its *`` 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 only advantage over a simpler ``import modu`` is that it will save a little
typing. typing.