-
Key: PYTH-19
-
Legacy Issue Number: 3430
-
Status: closed
-
Source: Humboldt-Universitaet ( Martin von Loewis)
-
Summary:
The adopted specification says that IDL modules map to Python modules,
and seems to imply that global modules are mapped to global modules
(without explicitly saying so). Is it conforming if the generated
module appear in an implementation-defined package? For example, to
access the CORBA module in ORB X, a number of implementations require
to writefrom X import CORBA
instead of
import CORBA
With this approach, it is possible to have multiple implementations of
CORBA installed, but it requires applications to specify which one
they want to use.Proposed resolution: In the section 1.2 (Scoped Names), add a
paragraphAn implementation can chose to map top-level definitions (including
the module CORBA) to modules in an implementation-defined package,
to allow concurrent installations of different CORBA runtime
libraries. In that case, the implementation must provide a
configuration option so that toplevel modules can be used without
without importing them from a package. -
Reported: PYTH 1.0b1 — Thu, 16 Mar 2000 05:00 GMT
-
Disposition: Resolved — PYTH 1.0
-
Disposition Summary:
Supporting multiple implementations is desirable, however, one of them must be selected as the defau
-
Updated: Fri, 6 Mar 2015 20:58 GMT