[Python-bugs-list] [ python-Bugs-534807 ] C extension modules with same short name

[noreply@sourceforge.net]

Bugs item #534807, was opened at 2002-03-25 19:54
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=534807&group_id=5470

Category: Extension Modules
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Tom Epperly (tepperly)
Assigned to: Nobody/Anonymous (nobody)
Summary: C extension modules with same short name

Initial Comment:
I am working on a language interoperability project,
http://www.llnl.gov/CASC/components/. We have an IDL
that gets converted into Python C extension modules. If
we have an IDL such as this:

package MPIB {
  interface Base {
  }
}

package MPIB.Default {
  class Base implements-all MPIB.Base {
  }
}

We end up with two C extension modules whose short name
is Base.  There is a symbol conflict when loading both
because they both use "initBase" as the DLL/SO
initialization function.  It would be nice if C
extension modules could use the fully qualified module
name instead of the short name for the initialization
function.  For example,

initMPID_Base and initMPIB_Default_Base 
or
initMPIDBase and initMPIDDefaultBase

What do you think?

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2002-03-27 13:32

Message:
Logged In: YES 
user_id=21627

I can't see why this gives a conflict. When Python loads the
module, it requests the symbol specifically from the shared
library it just loaded. What operating system are you using?

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2002-03-26 14:02

Message:
Logged In: YES 
user_id=6656

There is exactly no way in which this is a 2.2.1 candidate.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=534807&group_id=5470