Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Chris Angelico <rosuav@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Python programs and relative imports
Date: Sat, 9 Apr 2016 03:11:06 +1000
Lines: 23
Message-ID: <mailman.94.1460135468.2253.python-list@python.org>
References: <ndu70d$m0t$1@dont-email.me> <ne8o2e$van$1@dont-email.me> <CAPTjJmpNZkGE+eg_OnGYBw=0EDnGXq-KysE0qLiPNTp7NLATbA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
In-Reply-To: <ne8o2e$van$1@dont-email.me>
Precedence: list
Xref: csiph.com comp.lang.python:106694

On Sat, Apr 9, 2016 at 2:59 AM, Rob Gaddi
<rgaddi@highlandtechnology.invalid> wrote:
> Rob Gaddi wrote:
>
>> Does anyone know the history of why relative imports are only available
>> for packages and not for "programs"?  It certainly complicates life.
>>
>
> Really, no one?  It seems like a fairly obvious thing to have included;
> all of the reasons that you want to be explicit in saying:
>
>   from . import mypkg
>
> in a package apply just as well in an executable script.  But instead,
> they've got different semantics such that you expressly _cannot_ use
> relative imports in a script.  This feels like such a glaring oversight
> that there must have been some rationale behind it.

You can use the simple "import mypkg" syntax to load these up. I'm not
sure what you're looking for - do you want to prevent that syntax from
working, to prevent accidental shadowing?

ChrisA