RetroSearch Browse

Tue Apr 6 22:28:02 EDT 2004 · http://mail.python.org/pipermail/python-dev/2004-April/044142.html

On Tue, Apr 06, 2004, Greg Ewing wrote:
>
> Would it be unreasonable to define "." as meaning the current
> *package*, rather than the current *module* -- i.e. the package itself
> if the importer is a package, and the containing package if it's a
> plain module?

Not unreasonable, but I think it complicates the explanation.  I'm
basically -0 on having "." in __init__.py refer to the current package
instead of the parent; we'll see what Guido says.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

Why is this newsgroup different from all other newsgroups?

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2004-April/044142.html below:

[Python-Dev] Re: PEP 328 -- relative and multi-line import