[issue36614] Popen output on windows server 2019

Steve Dower added the comment: > I guess Popen is using some OS library or environment that has changed in > WS2019. Yep, which is why the report should go to those responsible for WS2019. If they say it's an intentional change and users are supposed to work around it themselves, then we

[issue36614] Popen output on windows server 2019

weispinc added the comment: The tool is outputing exactly the same file on both WS2019 and WS2016. I guess Popen is using some OS library or environment that has changed in WS2019. -- ___ Python tracker

[issue36614] Popen output on windows server 2019

Steve Dower added the comment: As we haven't done anything special for WS2019 yet, this is a change in Windows (or whatever tool is outputting the text). You could report it to Microsoft. I don't know the best way to report bugs in Windows Server though, but most people with it have support

[issue36614] Popen output on windows server 2019

Change by weispinc : Added file: https://bugs.python.org/file48264/popen.py ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36614] Popen output on windows server 2019

STINNER Victor added the comment: > Popen, when run on Windows server 2019 does not output binary by default. What do you mean by "binary"? -- nosy: +vstinner ___ Python tracker

[issue36614] Popen output on windows server 2019

SilentGhost added the comment: Could you add the code that you're running. -- components: +Library (Lib), Windows nosy: +SilentGhost, paul.moore, steve.dower, tim.golden, zach.ware title: Popen -> Popen output on windows server 2019 versions: +Python 3.7