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

Showing content from https://mail.python.org/pipermail/python-dev/2006-February/061747.html below:

[Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)

• Previous message: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)
• Next message: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

At 03:49 PM 2/23/2006 +1300, Greg Ewing wrote:
>Steven Bethard wrote:
> >  And, as you mention, it's consistent
> > with the relative import feature.
>
>Only rather vaguely -- it's really somewhat different.
>
>With imports, .foo is an abbreviation for myself.foo,
>where myself is the absolute name for the current module,
>and you could replace all instances of .foo with that.

Actually, "import .foo" is an abbreviation for "import myparent.foo", not 
"import myparent.myself.foo".

• Previous message: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)
• Next message: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4