swig/Examples/python/import_packages/same_modnames1
William S Fulton a9c6196f71 Display testname when running the import_packages Python examples
For easier identification of what is running in these examples.
2014-10-07 20:58:40 +01:00
..
pkg1 Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
pkg2 Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
Makefile Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
README Fixed SF bug #1297 (Python imports) 2013-12-24 17:22:25 +00:00
runme.py Display testname when running the import_packages Python examples 2014-10-07 20:58:40 +01: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.
  pkg2/foo.i - Pkg2_Foo class (derived from Pkg1_Foo).

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

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

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