A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-March/034172.html below:

python-dev Summary for 2003-03-01 through 2003-03-15)

[Python-Dev] capability-mediated modules (was: python-dev Summary for 2003-03-01 through 2003-03-15) [Python-Dev] capability-mediated modules (was: python-dev Summary for 2003-03-01 through 2003-03-15)Samuele Pedroni pedronis@bluewin.ch
Thu, 20 Mar 2003 13:41:07 +0100
>
> Making it explicit would make me happy. Can you pass parameters to an
> import?
>

not directly,

an extension like

import module(parmmod=....,...)

would not seem totally unreasonable.

The problem is that normally modules are uniquely globally identified
singletons, but the very notion of parametrization implies instantiation and
that breaks the singleton part. When to instatiate a new module and when not?

a potential problem is not simply module specific global state but that the
e.g. classes exported from two instances of the same module would be _distinct_
and so not interoperable.

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