I've been using a Python script to build a distribution file containing several PyInstaller-built exes. This has been working well, but it's broken by the reorganization in 1.5.

Here's what I've been doing:

   * Set blddir = the path to PyInstaller
   * append blddir to sys.path
   * Import Build
   * Set Build.HOMEPATH = blddir
   * For each folder containing one of the utliities to be built, do
     uname = path.basename(folder)
     Build.main(uname+'.spec', path.join(blddir, 'config.dat'))

Now Build.py lives in the utils subfolder, so the import above fails ("no module named Build"). I've tried changing path to the utils folder, but "import Build" crashes Python.

So, in the new scheme, what's the Right Way to invoke PyInstaller from a Python script? I suppose I could do an os.exec, but if there's a simple way to do it without spawning a process, I'd prefer it.

TIA,
--

Don Dwiggins
Advanced Publishing Technology


--
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyinstaller?hl=en.

Reply via email to