Issue 36614: Popen output on windows server 2019 (original) (raw)

Created on 2019-04-12 14:01 by weispinc, last changed 2022-04-11 14:59 by admin.

Messages (6)
msg340044 - (view)	Author: (weispinc)	Date: 2019-04-12 14:01
Popen, when run on Windows server 2019 does not output binary by default. Tried Python 3.5 3.6 3.7. OK on Windows server 2016 and 1012.
msg340045 - (view)	Author: SilentGhost (SilentGhost) *	Date: 2019-04-12 14:04
Could you add the code that you're running.
msg340047 - (view)	Author: STINNER Victor (vstinner) *	Date: 2019-04-12 14:08
> Popen, when run on Windows server 2019 does not output binary by default. What do you mean by "binary"?
msg340053 - (view)	Author: Steve Dower (steve.dower) *	Date: 2019-04-12 14:57
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 contacts.
msg340068 - (view)	Author: (weispinc)	Date: 2019-04-12 15:40
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.
msg340097 - (view)	Author: Steve Dower (steve.dower) *	Date: 2019-04-12 18:46
> 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 can do a workaround, but if it's unintentional then they should fix it.