swig/Examples/python/import_packages/same_modnames2
luz paz c8bec18554 Fix various typos
Found via `codespell -q 3 -L ans,anumber,ba,bae,chello,clos,cmo,coo,dout,fo,funktion,goin,inout,methid,nd,nin,nnumber,object,objekt,od,ois,packag,parm,parms,pres,statics,strack,struc,tempdate,te,thru,uint,upto,writen`
2022-04-11 07:59:36 +12: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 Fix various typos 2022-04-11 07:59:36 +12: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