Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81850 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2014-12-03 22:02 +1100 |
| Last post | 2014-12-03 22:02 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
Style question: Importing modules from packages - 'from' vs 'as' Chris Angelico <rosuav@gmail.com> - 2014-12-03 22:02 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-12-03 22:02 +1100 |
| Subject | Style question: Importing modules from packages - 'from' vs 'as' |
| Message-ID | <mailman.16525.1417604545.18130.python-list@python.org> |
When importing a module from a subpackage, it's sometimes convenient to refer to it throughout the code with a one-part name rather than two. I'm going to use 'os.path' for the examples, but my actual use-case is a custom package where the package name is, in the application, quite superfluous. Throughout the code, I want to refer to "path.split()", "path.isfile()", etc, without the "os." in front of them. I could do either of these: import os.path as path from os import path Which one would you recommend? Does it depend on context? An "as" import works only if it's a module in a package, where the "from" import can also import other objects (you can't go "import pprint.pprint as pprint"). I'm fairly sure that's an argument... on one side or another. :) Thoughts? ChrisA
Back to top | Article view | comp.lang.python
csiph-web