swig/Examples/python/import_packages/relativeimport2
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
..
py2 Remove use of preinst-swig script 2015-08-21 22:43:17 +01:00
py3 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 -relativeimport option.

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

Overview:
---------

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

     pyX/pkg2/pkg3/pkg4/foo.i  - Pkg4_Foo class
     pyX/pkg2/bar.i            - Pkg2_Bar class derived from Pkg4_Foo

The difference between this ('relativeimport2') case and the case
'relativeimport1' is the "distance" between importer and importee.

If everything works well, the package pyX.pkg2 shall load properly.

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