swig/Examples/python/import_packages/relativeimport2
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
..
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 Default to running tests with Python 3 2022-03-17 18:55:10 +13: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 -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