From: Mast3rMind <oli...@gm...> - 2011-11-23 20:18:46
|
It seems what I want to achieve cannot be done easily. Instead, I chose to create multiple projects wrapping portions of my big monolithic project. This was more recommended practice. Mast3rMind wrote: > > Hi everyone, > > I'm trying to create multiple modules in the same package, linked to the > same ".pyd" file, ie I don't want to have a different "pyd" for each > module. > > Here is what I want: > > mypackage/ > > __init__.py > module1.py > module2.py > > And I want to use only one ".pyd" located at the same place than the > folder > "mypackage". > > I currently have two interface files: module1.i and module2.i, everything > compiles fine, but I try to import my package in Python, I receive the > following error: > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "D:\Dev\mypackage\__init__.py", line 1, in <module> > import module1 > File "D:\Dev\mypackage\module1.py", line 30, in <module> > _app = swig_import_helper() > File "D:\Dev\mypackage\module1.py", line 22, in swig_import_helper > import _module1 > ImportError: No module named _module1 > > I've tried the option "package" in each module.i file, but this option > doesn't seem to do anything. > > %module(package="mypackage",docstring=DOCSTRING) module1 > > Any thought would be appreciated. Thanks in advance, > > Olivier > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Swig-user mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-user > > -- View this message in context: http://old.nabble.com/Multiple-modules-in-the-same-package-%28pyd%29-tp32841093p32874498.html Sent from the swig-user mailing list archive at Nabble.com. |