swig/Examples/python/import_packages/same_modnames2
William S Fulton 4fb940d913 Further fixes when using type() when using -builtin to include module name
Using type() on a builtin type should include the package and module
name, see http://docs.python.org/2/c-api/typeobj.html
2014-03-01 23:26:27 +00:00
..
pkg1 Fixed SF bug #1297 (Python imports) 2013-12-24 17:22:25 +00:00
Makefile Fixed SF bug #1297 (Python imports) 2013-12-24 17:22:25 +00:00
README Fixed SF bug #1297 (Python imports) 2013-12-24 17:22:25 +00:00
runme.py Further fixes when using type() when using -builtin to include module name 2014-03-01 23:26:27 +00:00

This example tests the %import directive and working with multiple modules.

There are two modules having same name but belonging to different packages.
This case is not correctly handled by swig 2.

The issue was reported as Source Forge bug #1297 and later as GitHub issue #7.

Use 'python runme.py' to run a test.

Overview:
---------

The example defines 2 different extension modules--each wrapping a separate C++
class.

     pkg1/foo.i       -  Pkg1_Foo class
     pkg1/pkg2/foo.i  -  Pkg2_Foo class derived from Pkg1_Foo

The pkg1/pkg2/foo module uses %import to refer to pkg1/foo.

If everything works well, the module pkg1.pkg2.foo shall load properly.

Unix:
-----
- Run make
- Run the test as described above