I will have to take a look into Biopython to search for any hidden imports.
-W On Tue, 2006-04-11 at 01:35 +0200, no_carrier wrote: > Thanks William, > in the meanwhile I went ahead compiling scripts and only running them > on the same linux distro as that used to compile them (but not same > computer and the destination computer has a different version of > python installed). I found that this restriction was still acceptable > for my project. > > On the same distro (different computer, different installed python), > pyinstaller worked for simple scripts, however when I threw in > Biopython, the compiled script started giving an error, right at the > beginning before executing anything else. (see below the error). > > Even when I try to run the compiled script on the SAME machine used to > compile (different directory) it gives the same error. On such machine > the default python is 2.2, while the one used to compile is installed > in /opt and is not the default and it is 2.4 . > > These are my only includes: > import sys, re, os, os.path, cPickle, math > from Bio.Blast import NCBIStandalone > This is the error: > [EMAIL PROTECTED] tmpaBsqYb2]$ step1 > Traceback (most recent call last): > File "<string>", line 4, in ? > File "/home/me/pyinstaller/iu.py", line 312, in importHook > mod = _self_doimport(nm, ctx, fqname) > File "/home/me/pyinstaller/iu.py", line 398, in doimport > exec co in mod.__dict__ > File "/home/me/PItries/step1src/buildstep1/out1.pyz/Bio", line 48, > in ? > File "/home/me/PItries/step1src/buildstep1/out1.pyz/Bio", line 36, > in _load_registries > OSError: [Errno 20] Not a directory: > '/home/me/PItries/step1src/buildstep1/out1.pyz' > > > Note that "/home/me/PItries/step1src" is the directory of the script > at the time of compilation. The directory where I was running it is > totally different. > > I have no clue of what that error and stack trace are telling me. Any > explanation or idea to work around it? > > Thanks in advance > > PS: In attachment you can see the compilation warnings file. I notice > that that there are many top-level import failures (Some in Bio but > not in Bio.Blast, dunno if this is meaningful), but I have no clue of > how to fix these either...? > > > > William Caban wrote: > > I still working with this issue. I'm trying to completely port this > > section to distutils in order to finally clean the code. I'm still > > having some issues with the generated loader and I'm working with it. > > > > -William > > > > On Fri, 2006-04-07 at 12:56 -0400, William Caban wrote: > > > > > [...] > > > On Thu, 2006-04-06 at 23:07 +0200, no_carrier wrote: > > > > > > > This is my first use of pyinstaller. > > > > I have made a kind of helloworld python [...] > > _______________________________________________ > PyInstaller mailing list > [email protected] > http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller _______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
