Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Carl Meyer <carl@oddbird.net>
Newsgroups: comp.lang.python
Subject: Re: Importing two modules of same name
Date: Tue, 9 Feb 2016 16:36:41 -0700
Lines: 74
Message-ID: <mailman.2.1455063648.7749.python-list@python.org>
References: <20160209232303.GC2583@mail.akwebsoft.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VGgOO1RwpiFLT76SjUVBxnweDo9tUuk2t"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
In-Reply-To: <20160209232303.GC2583@mail.akwebsoft.com>
Precedence: list
Xref: csiph.com comp.lang.python:102738

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--VGgOO1RwpiFLT76SjUVBxnweDo9tUuk2t
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Tim,

On 02/09/2016 04:23 PM, Tim Johnson wrote:
> Before proceding, let me state that this is to satisfy my
> curiousity, not to solve any problem I am having.
>=20
> Scenario :
> Web application developed at /some/dir/sites/flask/
>=20
> If I have a package - let us call it app and in my
> /some/dir/sites/flask/app/__init__.py is the following:
>=20
> from config import config
>=20
> imports the config dictionary from  /some/dir/sites/flask/config.py
>=20
> (the real-case scenario is M. Grinberg's tutorial on Flask).
>=20
> What if I wanted to add a module in the app package and call it from
> __init__.py
>=20
> That entails having two modules name config
> one at /some/dir/sites/flask/config.py
> and the other at /some/dir/sites/flask/app/config.py
>=20
> What would be the proper way to do this? (If proper at all :)) I
> realize that it may not be best practices. And is a practice that I
> avoided in the past.

The proper way to do this in Python 2.7 is to place `from __future__
import absolute_import` at the top of flask/app/__init__.py (maybe best
at the top of every Python file in your project, to keep the behavior
consistent). Once you have that future-import, `import config` will
always import the top-level config.py. To import the "local" config.py,
you'd either `from . import config` or `import app.config`.

Python 3 behaves this way without the need for a future-import.

If you omit the future-import in Python 2.7, `import config` will import
the neighboring app/config.py by default, and there is no way to import
the top-level config.py.

Carl


--VGgOO1RwpiFLT76SjUVBxnweDo9tUuk2t
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJWungNAAoJEC0ft5FqUuEh+ZMQAJRNYAcA8VUUEPDNe5GRj+25
csAJCcWimxHXTWIRtOuiwoaLg16DSU6vkllxm4DeSjy5XuNxqrYli+Mh8+T7YSh2
bREt4iu7ftq1jzEtDbA0zjqnQ6KZd78mKWwxZKkuVcFkQg14nUPX8+1yUI7+8SiJ
korWQpLukRgwwl6oW0+YW7BnR1Z7RBKvCAGbetduSSjfSkYmvLHFKfljp84EAD/P
jD7x4erb6KIGsmiIw/IQ8G/OGiuGsFPBlcWA4idFx4HoWD74dzk0W5FcjnLEYg8d
dxBswlUhvYmnKdl3bnLYjAiTASgzc8G03YjyNiT7Ab8+y1sMukSNJiZkTLkKP7A9
4lt2pPeR5tGYv4P3qDBk97lzBf5KeWDujuCdUcfU1tKBuvNuiHpH0jOhxH6XiBUq
1wFRlkGM6kTLF3WOd895LEGgOamJHGbChuislP9mu40Y3/ibug3LM866MrWb9Xtj
rC4I8Kjnb4vL3YZirRddFpNkLedW/+yM9pjgjbXBb7KSwfBjNd/FbnJ1rBHkASXc
dQ5/tm8A5ffSsWydeAnjstgcrF3JfntzdjMBM/tugiXI3VDq3ARmqIqvLaVBt96G
9ae6xDiR7EeduTo/sROYqKmQSUFVYf0ROdSS7mLI2HE9dMQwWzzAhdUZx87OZRCE
4hr/C/uD8Yx1G76MxvsN
=M86D
-----END PGP SIGNATURE-----

--VGgOO1RwpiFLT76SjUVBxnweDo9tUuk2t--