From: Philip S. <ph...@se...> - 2011-09-06 18:06:32
|
On Sep 1, 2011, at 3:17 PM, Carsten Grohmann wrote: > Am Donnerstag, 18. August 2011 schrieb Philip Semanchuk: >> On Aug 16, 2011, at 12:36 AM, Carsten Grohmann wrote: >>> Hi Philip, >>> >>> Am Dienstag, 9. August 2011 schrieb Philip Semanchuk: >>>> "Y:\duke\src\vespa\common\wx_gravy\widgets\floatspin_multiplier\floatspi >>>> n_ property.py", line 13, in <module> from >>>> vespa.common.wx_gravy.widgets.floatspin.floatspin import EVT_FLOATSPIN >>>> File "c:\Programme\pyinstaller-1.5\iu.py", line 455, in importHook >>>> ImportError: No module named vespa >>> >>> Looks like works as designed :-/ >>> I think pyinstaller changes the Python search path and the vespa module >>> won't be found after that. >> >> Changing the path sounds a bit rude but there are usually good reasons for >> such things. > > It really works as designed. Because PyInstaller collects all data need by the > specified python files incl. all dependencies and build a specific Python > installation. This stipped installation doesn't know anything about the python > installation it comes from. No search path. > > That's why the current PyInstaller couldn't import the vespa module. > > I think about building two Windows installer > 1) a wxglade stand alone edition (the current rc3) > 2) a wxglade full edition using the local Python and wxPython setup > > What do you think about this suggestion? Sounds good to me. |