dhermes / appveyor-py-launcher Goto Github PK

I think the real issue is that Python is writing to something that is neither stdout or stderr. How do I know this? I exported the AppVeyor py.exe as a build artifact and am using it on my local machine.

Luckily on my local machine, it exhibits the same behavior with 32-bit 3.5 and 32- and 64-bit 3.6. And it respects PYLAUNCH_DEBUG. But when I try to capture to a file via

>.\py -3.5-32 -V > 3.5-32.txt 2>&1

the file is empty.

I did capture the debug output of each and will start to investigate now:

• 3.5-32.txt
• 3.5-64.txt
• 3.6-32.txt
• 3.6-64.txt