Am 31.01.2017 um 21:24 schrieb Coyot Linden (Glenn Glazer): > So my questions two are: > > 1) Any idea on how to coax more information into CalledProcessError to > see what is going on?
a) When trying to reproduce this in an interacrive console, I get output at stdout (or stderr, I did not verify). Maybe your framework is catching this? b) If you lokk at the code of check_call, you can see that not output is passed to CallProcessError. c) Try another function in subprocess to fetch the output of the process. > 2) More directly, what is failing here? You are passing options with trailing spaces, e.g. "--log-level " and "-p ". BTW: If your build-com.py is known to always use the same Python version as PyInstaller, you may use PyInstaller.__main__.run(["-y", "-w", …]) -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/warum-sie-nicht-perl-programmiern-sollten Kolumne: http://www.cissp-gefluester.de/2010-06-adobe-und-der-maiszunsler -- 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 https://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
