Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 6062

Summary: Multiple shared libraries with same methods defined
Product: [Retired] Red Hat Linux Reporter: mike.olson
Component: pythonAssignee: Matt Wilson <msw>
Severity: high Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-11-18 23:40:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description mike.olson 1999-10-18 18:49:42 UTC
I have 2 shared libraries that both define symbols of the
same name.  When I import these modules into python and call
the method with the shared name, I always exectue the method
of the last module imported.

Ex: If I have 2 shared modules written in C, each with a
different module name, but both having a function called
foo, the following code breaks.

import A
import B #Really calls

My code that uses this was originally written and worked
with the non-redhat rpms available at


Comment 1 Michael K. Johnson 1999-11-18 23:40:59 UTC
Not Found

The requested URL /python/files/python-1.5.2-2.src.rpm was not found
on this server.

Binary rpms don't do us much good...  :-)

Unfortunately, the patch that I believe breaks this for you appears
to have been added to fix something else.  I'm assigning this bug
to the developer who added that patch.  (Matt, it's
python-1.5.2-dl-global.patch -- what's this about libtool, and why
is the patch there in the first place?)

Comment 2 Matt Wilson 2001-01-27 02:08:46 UTC
Unfortunately I can't address this until we start using the Python 2.0 package.