Application and package of the same name

[Chris Angelico]

On Fri, Oct 20, 2017 at 7:09 AM, Skip Montanaro
<skip.montanaro at gmail.com> wrote:
>> My immediate reaction is "you shouldn't name your main program and
>> your package the same". It's not a pattern I've seen commonly used.
>>
>> However, the approaches I've seen used (a __main__.py inside the
>> package, so you can execute it via `python -m fribble`, or a setup.py
>> entry point to generate a script wrapper for the application) may be
>> more common among people focused more on library development than on
>> application development.
>
> Thanks Paul. The simplest course for me is to change the name of the
> application,
> as the package is already in use by other people, and I don't really
> want to embed the
> application in the package.
>

Have you toyed with "from __future__ import absolute_import" ? Not
sure if it'd help or not, but worth a try.

ChrisA