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
22 lines
596 B
Text
22 lines
596 B
Text
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
|