5562deec62
This changeset resolves several issues related to python imports.
For example, it's possible now to import modules having same module
names, but belonging to different packages.
From the user's viewpoint, this patch gives a little bit more control on
import directives generated by swig. The user may choose to use relative
or absolute imports (docs are provided in separate PR).
Some details:
- we (still) generate import directives in form 'import a.b.c' which
corresponds to absolute imports in python3 and (the only available)
ambiguous one in python2.
- added -relativeimport option to use explicit relative import syntax
(python3),
Tests are under Examples/python, these are in fact regression tests but
with the current swig testing framework it seems to be impossible to put
appropriate tests under test-suite.
Closes #7
26 lines
700 B
Text
26 lines
700 B
Text
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.
|