I actually used my own Hello World example: --------- hello.py -------------- print "Hi" -------------------------------------
Seems like that shouldn't crash, unless I've got something screwed up. ;-) I'm not sure if the first ~50 lines will be useful (I get a few 100) but here they are (followed by the tail): C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56>python pyinstaller.py --log=DEBUG hello.py 46 INFO: wrote C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56\hello\hello.spec 69 INFO: Testing for ability to set icons, version resources... 118 INFO: ... resource update available 119 DEBUG: Testing for UPX ... 122 INFO: UPX is not available. 122 DEBUG: Computing PYZ dependencies 125 DEBUG: Analyzing pyi_importers C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56\PyInstaller\d epend\imptracker.py:332: DeprecationWarning: BaseException.message has been depr ecated as of Python 2.6 if not hookmodnm in e.message: 131 DEBUG: Analyzing pyi_archive 138 DEBUG: Analyzing pyi_archive.ZlibArchive 138 DEBUG: Analyzing imp 139 DEBUG: Analyzing sys 141 DEBUG: Analyzing pyi_archive.ArchiveReadError 141 DEBUG: Analyzing pyi_os_path 144 DEBUG: Analyzing marshal 145 DEBUG: Analyzing os 167 INFO: Processing hook hook-os 168 DEBUG: Analyzing struct 174 DEBUG: Analyzing subprocess 187 DEBUG: Analyzing os.path 187 DEBUG: Analyzing os.path 188 DEBUG: Analyzing os.path 188 DEBUG: Analyzing copy_reg 195 DEBUG: Analyzing os.path 197 DEBUG: Analyzing os.path 197 DEBUG: Analyzing os.path 197 DEBUG: Analyzing os.path 198 DEBUG: Analyzing posix 204 DEBUG: Analyzing nt 205 DEBUG: Analyzing nt._exit 207 DEBUG: Analyzing posix 213 DEBUG: Analyzing os.path 213 DEBUG: Analyzing posix 220 DEBUG: Analyzing os.path 220 DEBUG: Analyzing os.path 220 DEBUG: Analyzing warnings 230 DEBUG: Analyzing errno 231 DEBUG: Analyzing posixpath 241 DEBUG: Analyzing UserDict 250 DEBUG: Analyzing os.path 250 DEBUG: Analyzing _emx_link 256 DEBUG: Analyzing ntpath 266 DEBUG: Analyzing os.path 266 DEBUG: Analyzing os2emxpath 273 DEBUG: Analyzing _emx_link 279 DEBUG: Analyzing os.path 279 DEBUG: Analyzing gc 280 DEBUG: Analyzing _subprocess 282 DEBUG: Analyzing types 287 DEBUG: Analyzing fcntl 293 DEBUG: Analyzing threading 306 DEBUG: Analyzing msvcrt 307 DEBUG: Analyzing traceback 316 DEBUG: Analyzing _subprocess.CREATE_NEW_CONSOLE 316 DEBUG: Analyzing select 322 DEBUG: Analyzing signal 322 DEBUG: Analyzing pickle 339 DEBUG: Analyzing collections 346 DEBUG: Analyzing _threading_local 353 DEBUG: Analyzing _threading_local.local 353 DEBUG: Analyzing traceback.format_exc 355 DEBUG: Analyzing collections.deque 355 DEBUG: Analyzing thread 356 DEBUG: Analyzing thread._local 356 DEBUG: Analyzing random 368 DEBUG: Analyzing random.random 369 DEBUG: Analyzing time 371 INFO: Processing hook hook-time 371 DEBUG: Analyzing time.time 371 DEBUG: Analyzing thread.stack_size 372 DEBUG: Analyzing time.sleep 372 DEBUG: Analyzing functools 378 DEBUG: Analyzing functools.wraps 379 DEBUG: Analyzing _abcoll 389 DEBUG: Analyzing keyword 395 DEBUG: Analyzing keyword.iskeyword 397 DEBUG: Analyzing operator 398 DEBUG: Analyzing operator.itemgetter 398 DEBUG: Analyzing cPickle [********lots more like that, then ... **********] 2332 DEBUG: Analyzing posix 2338 DEBUG: Analyzing nt.listdir 2339 DEBUG: Analyzing nt.environ 2341 DEBUG: Analyzing posix 2345 DEBUG: Analyzing posix 2352 DEBUG: Analyzing pyi_archive.ZlibArchive 2352 DEBUG: Analyzing pyi_archive.ArchiveReadError 2353 DEBUG: Analyzing _struct.__doc__ 2355 DEBUG: Analyzing _struct._clearcache 2368 INFO: Extending PYTHONPATH with C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56 2369 INFO: checking Analysis 2473 INFO: checking PYZ 2533 INFO: checking PKG 2536 INFO: building because C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyins taller-e99cc56\hello\build\hello\hello.exe.manifest changed 2539 INFO: building PKG (CArchive) out00-PKG.pkg 2578 INFO: checking EXE 2579 INFO: rebuilding out00-EXE.toc because pkg is more recent 2580 INFO: building EXE from out00-EXE.toc 2583 INFO: Appending archive to EXE C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56\hello\build\hello\hello.exe 2631 INFO: checking COLLECT WARNING: The output directory "C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-py installer-e99cc56\hello\dist\hello" and ALL ITS CONTENTS will be REMOVED! Continue? (y/n)y 13443 INFO: Removing dir C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56\hello\dist\hello 13697 INFO: building COLLECT out00-COLLECT.toc C:\Gary\P-smartmed\2014-03-plotter\pyinstaller-pyinstaller-e99cc56> BUT, and this is crazy, the above (running it with DEBUG) actually generated hello.exe(!). And the executable ran, printing Hi. So I deleted the hello/ directory entirely and tried again without the DEBUG option, and now that runs fine and generates a working hello.exe as well. So, then I went for gold and tried to build an EXE that uses matplotlib (my target to begin with) ... and by joe, it worked! So, whatever was wrong somehow got fixed. Thank you ... though my apologies for perhaps not being able to provide you info for a double-check.Thinking windoze-like, could I have failed to reboot at the right time after install or something? Just a random thought (I have restarted a couple times through this process, but I can't timeline them precisely enough to be helpful) ... -best Gary On Saturday, March 22, 2014 4:05:19 PM UTC-4, Hartmut Goebel wrote: > > Am 21.03.2014 13:51, schrieb Gary Strangman: > > I tried out the Hello World example > > Well, which Hello World example? At least the one you are using is not a > simple one, as it seam to import al lot of modules, exp. both PyQT4 and > tkinter. > > Anyway, when looking at the stack-trace, it tracks down to this statement > failing: > > self.out = os.path.join(WORKPATH, 'out%02d-%s.toc' % > (self.invcnum, self.__class__.__name__)) > > Since this join only two string, of which the second is a constant string, > this means the for any reason WORKPATH is None. When digging into the > stack-trace even more, it shows, that the hooks are called during the > setup-phase (configure.py", line 146, in get_config: > find_PYZ_dependencies(config)). > > So, this is a very, very interesting case. For me it looks like your setup > is somehow mixed up somehow. Nevertheless I'd like to find the reason so we > can try to implement a check for this. > > Please run pyinstaller with --log=DEBUG and post the first approx. 50 > lines of output. Additionally please check your installation, esp. if > there is stuff in the pyinstaler-checkout which does not belong here. > > > -- > Schönen Gruß > Hartmut Goebel > Dipl.-Informatiker (univ), CISSP, CSSLP > Information Security Management, Security Governance, Secure Software > Development > > Goebel Consult, Landshut > http://www.goebel-consult.de > > Blog: http://www.goebel-consult.de/blog/quelltext-fur-tolino-shine > Kolumne: > http://www.cissp-gefluester.de/2010-11-it-sicherheit-im-unternehmen-eine-interne-oder-externe-angelegenheit > > > Goebel Consult ist Mitglied bei http://www.7-it.de/ > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
