|
On 1/31/17 13:50, Hartmut Goebel wrote:
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.
Ah ha! Sharp eyes, my friend.
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. |
- [PyInstaller] running pyinstaller from python Coyot Linden (Glenn Glazer)
- Re: [PyInstaller] running pyinstaller fro... Hartmut Goebel
- Re: [PyInstaller] running pyinstaller... Coyot Linden (Glenn Glazer)
