A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-December/030677.html below:

[Python-Dev] New universal import mechanism ( Re: [Python-checkins] python/dist/src/Python import.c,2.210,2.211)

[Python-Dev] New universal import mechanism ( Re: [Python-checkins] python/dist/src/Python import.c,2.210,2.211)Samuele Pedroni pedronis@bluewin.ch
Tue, 3 Dec 2002 15:48:12 +0100
From: "David Abrahams" <dave@boost-consulting.com>
> "Samuele Pedroni" <pedronis@bluewin.ch> writes:
...
> > What about
> >
> > from module import x
>
> I had the same thoughts. I am not entirely convinced that what my user
> has asked for is the best approach.
>
> > if the importing module has already a defined x then maybe that
> > should be also under user control?
>
> I don't understand that suggestion. Care to elaborate?
>

my point is that if you offer a way to hook into the behavior of from import *
then you need for completeness and to establish a coherent whole to offer a
hook also in

from import foo,bar

regards.




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