swig/Examples/python/import_packages/same_modnames1
William S Fulton 604ae7186b Fix for running 'python -m' when using swig -builtin
Same as e05b5ea for -builtin.

Also added runtime tests to check 'python -m'.
2018-12-04 19:12:13 +00:00
..
pkg1 Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
pkg2 Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
Makefile Remove realpath from python/import_packages example 2015-08-20 06:19:12 +01:00
README Fixed SF bug #1297 (Python imports) 2013-12-24 17:22:25 +00:00
runme.py Fix for running 'python -m' when using swig -builtin 2018-12-04 19:12:13 +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.
  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.