[Grok-dev] Re: Module with the same name as package

Martijn Faassen faassen at startifact.com
Fri Jan 19 07:02:27 EST 2007

Philipp von Weitershausen wrote:
> Jan-Wijbrand Kolman wrote:
>>> Let's say you have a package called 'herd' and in that package you have
>>> a module with the same name 'herd/herd.py'.
>> <snip>
>> FYI: Yesterday Martijn and I bumped to this issue as well, but more
>> related to import statement and relative imports. I was about to add
>> an issue in the launchpad bugtracker when your posting arrived. I
>> reported the issue in the bug tracker anyway (esp. since people using
>> grokproject will have this situation by default):
>>  https://bugs.launchpad.net/grok/+bug/80403
> Dagnabbit. So we also need to find a sensible name for the skeleton 
> module in a package created by grokproject.
> This is really all Python's fault, not supporting absolute imports... GAH!

Python 2.5 does have a way:


Doesn't help us though, and it requires a /from __future__ import 
absolute_import' anyway, so at this point not really beginner friendly.



More information about the Grok-dev mailing list