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
..
pkg1	Something optimizes out empty files and breaks the tests. Put something in.	2016-06-03 01:30:43 -06:00
foo.i	The Python module import logic has changed to stop obfuscating real ImportError problems.	2018-12-16 16:41:39 +00:00
Makefile	Fix out of source clean target in import_packages Makefile	2018-01-07 00:57:23 +00:00
runme.py	Skip Python subprocess calls in import_packages testcase on Windows	2018-12-06 06:50:57 +00:00