swig/same_modnames2 at f8ed9d71a76db33dfd341e7749bbe958dfd276ec - swig

History

William S Fulton ff93f2e26e Skip Python subprocess calls in import_packages testcase on Windows Getting these kind of errors on Appveyor which uses mingw/cygwin to run a Python interpreter: Native windows Python 3.6 running under cygwin and mingw Python 3.7 running under mingw: Fatal Python error: _Py_HashRandomization_Init: failed to get random numbers to initialize Python Cygwin Python 2.7 running under cygwin: 0 [main] python2.7 496 child_info_fork::abort: address space needed by '_foo.dll' (0x6D0000) is already occupied		2018-12-06 06:50:57 +00:00
..
pkg1	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	Skip Python subprocess calls in import_packages testcase on Windows	2018-12-06 06:50:57 +00:00

README

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