Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81951
| References | <CAPTjJmo1-QCgcbsjKNgH3oN-nm5qjB5GrvCiC6Qc9p+S8cNjpg@mail.gmail.com> <2047880662.4611734.1417714597653.JavaMail.root@sequans.com> <CAPTjJmpgM2n=AdY+8gZ40gqe1S2zfD83Ui-f5SngRYLA3jMtCQ@mail.gmail.com> <m5qhqd$bts$1@ger.gmane.org> |
|---|---|
| Date | 2014-12-05 08:30 +1100 |
| Subject | Re: Style question: Importing modules from packages - 'from' vs 'as' |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.16589.1417728663.18130.python-list@python.org> (permalink) |
On Fri, Dec 5, 2014 at 7:56 AM, Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> wrote: > On 04.12.2014 19:05, Chris Angelico wrote: >> >> >> With os.path it definitely is. With the actual code in question, it's >> a Python 2.7 project that mostly uses relative imports - inside >> package.module1 is "import module2" etc - and I was writing an >> external script that calls on one of the modules. > > > What ? I'm usually thinking Python 3 not 2 and I'm never sure which Python > 2.x has backported which feature of 3, but I thought implicit relative > imports like you seem to describe are not working in 2.7 ? Hmm, I'm not sure, but certainly it does seem to work that way. Typing "import foo" from inside a package will import foo.py from the package directory. I haven't dug into the details of _why_, and if ever the project shifts to Python 3 (which I would like it to), we might have to change some of the import lines, but I'd still like to be able to reference "foo.bar" as meaning the "bar" top-level object in foo.py. ChrisA
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Style question: Importing modules from packages - 'from' vs 'as' Chris Angelico <rosuav@gmail.com> - 2014-12-05 08:30 +1100
csiph-web