Re: "from module import data; print(data)" vs "import module; print(module.data)"

Path	csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Gregory Ewing <greg.ewing@canterbury.ac.nz>
Newsgroups	comp.lang.python
Subject	Re: "from module import data; print(data)" vs "import module; print(module.data)"
Date	Fri, 26 Feb 2016 11:20:14 +1300
Lines	14
Message-ID	<dj9d10F4gciU1@mid.individual.net> (permalink)
References	<mailman.111.1456362461.20994.python-list@python.org> <535b56b5-f836-4cd6-ae95-33f18004c90b@googlegroups.com>
Mime-Version	1.0
Content-Type	text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding	7bit
X-Trace	individual.net MBdwwGctYOE5mHigywhbtQu/0uSXNFURlizwQbCdN7QN7dIX/s
Cancel-Lock	sha1:e2GYcJQigSEmKlr5ypz0QnSrIL4=
User-Agent	Mozilla Thunderbird 1.0.5 (Macintosh/20050711)
X-Accept-Language	en-us, en
In-Reply-To	<535b56b5-f836-4cd6-ae95-33f18004c90b@googlegroups.com>
Xref	csiph.com comp.lang.python:103520

Show key headers only | View raw

sohcahtoa82@gmail.com wrote:
> Now, I've noticed people talking about importing os.path.  Is there any
> reason to use "import os.path" rather than "import os"?  Both of them will
> still put the "os" module into the global namespace.

In the case of os.path it doesn't matter, because the
os module imports the appropriate path module automatically.

But in general, importing a package won't necessarily
import submodules under it, so sometimes you need to
import somepackage.somemodule explicitly.

-- 
Greg

Thread

"from module import data; print(data)" vs "import module; print(module.data)" Dan Stromberg <drsalists@gmail.com> - 2016-02-24 17:07 -0800
  Re: "from module import data; print(data)" vs "import module; print(module.data)" Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-02-25 14:39 +1100
    Re: "from module import data; print(data)" vs "import module; print(module.data)" Dan Stromberg <drsalists@gmail.com> - 2016-02-25 08:15 -0800
    Re: "from module import data; print(data)" vs "import module; print(module.data)" Dan Stromberg <drsalists@gmail.com> - 2016-02-25 08:20 -0800
    Re: "from module import data; print(data)" vs "import module; print(module.data)" Ethan Furman <ethan@stoneleaf.us> - 2016-02-25 08:35 -0800
    Re: "from module import data; print(data)" vs "import module; print(module.data)" Ethan Furman <ethan@stoneleaf.us> - 2016-02-25 08:51 -0800
  Re: "from module import data; print(data)" vs "import module; print(module.data)" sohcahtoa82@gmail.com - 2016-02-25 12:00 -0800
    Re: "from module import data; print(data)" vs "import module; print(module.data)" Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-02-26 11:20 +1300
      Re: "from module import data; print(data)" vs "import module; print(module.data)" Ben Finney <ben+python@benfinney.id.au> - 2016-02-26 10:38 +1100
        Re: "from module import data; print(data)" vs "import module; print(module.data)" Steven D'Aprano <steve@pearwood.info> - 2016-02-26 11:40 +1100
          Re: "from module import data; print(data)" vs "import module; print(module.data)" Ian Kelly <ian.g.kelly@gmail.com> - 2016-02-25 20:56 -0700
          Re: "from module import data; print(data)" vs "import module; print(module.data)" Chris Angelico <rosuav@gmail.com> - 2016-02-26 15:11 +1100
          Re: "from module import data; print(data)" vs "import module; print(module.data)" Ben Finney <ben+python@benfinney.id.au> - 2016-02-26 15:37 +1100

csiph-web