On 1/31/17 13:50, Hartmut Goebel wrote:
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?

Possibly, I will need to dig.

b) If you lokk at the code of check_call, you can see that not output is passed to CallProcessError.

The docs also say this, though it is kind of buried.  The distinction between _call and _output is buried in the definition of the error, not the methods.

c) Try another function in subprocess to fetch the output of the process.

Yup.  Tried an "dir Q:" and got None because it was _call.  I've converted instances of using _call to _output.


2) More directly, what is failing here?

You are passing options with trailing spaces, e.g. "--log-level " and "-p ".

Ah ha!  Sharp eyes, my friend. 

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", …])


Even better!  That's not only more pythonic, but also faster in that I am not forcing python to shell out.

Thanks much!

coyot

GLENN GLAZER | Senior Software Engineer
m:
562.305.2920 | email:  [email protected] | Second Life: Coyot Linden
LINDEN LAB | Create Virtual Experiences

--
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.

Reply via email to