swig/Doc
William S Fulton 03323f5c8b The Python module import logic has changed to stop obfuscating real ImportError problems.
Only one import of the low-level C/C++ module from the pure Python module is
attempted now. Previously a second import of the low-level C/C++ module was attempted
after an ImportError occurred and was done to support 'split modules'. A 'split module' is
a configuration where the pure Python module is a module within a Python package and the
low-level C/C++ module is a global Python module. Now a 'split module' configuration is
no longer supported by default. This configuration can be supported with a simple
customization, such as:

  %module(package="mypackage", moduleimport="import $module") foo

or if using -builtin:

  %module(package="mypackage", moduleimport="from $module import *") foo

instead of

  %module(package="mypackage") foo

See the updated Python chapter titled "Location of modules" in the documentation.

Closes #848 #1343
2018-12-16 16:41:39 +00:00
..
Devel Merge branch 'vadz-doxygen' 2018-06-07 08:13:10 +01:00
Manual The Python module import logic has changed to stop obfuscating real ImportError problems. 2018-12-16 16:41:39 +00:00
README suggest starting points for documentation 2008-10-09 22:42:45 +00:00

Doc/Manual    -  Latest version of the SWIG user manual
Doc/Devel     -  Developer documentation concerning SWIG internals.
                 (not necessarily up to date)

Open the index.html file in each of these directories with a web browser.