This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients eryksun, iMath, mmaswg, ohno, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-10-29.14:25:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> There's nothing gained by complicating this API with more options.

Yes, both options is too much. I suggested force_hide_console as an alternative to force_hide, not for both to be implemented. It would be the same as CreateNoWindow in .NET ProcessStartInfo [1], but ProcessStartInfo also has WindowStyle, and one or the other is ignored depending on the value of UseShellExecute. I see a lot of confusion online regarding these .NET ProcessStartInfo properties, which is something I'd like to avoid.

A benefit of force_hide based on wShowWindow=SW_HIDE is feature parity with ShellExecuteExW(), if subprocess ever supports the shell API. ShellExecuteExW() does not support CREATE_NO_WINDOW, but it supports a show-window command and CREATE_NEW_CONSOLE (i.e. the inverse of SEE_MASK_NO_CONSOLE).

Date User Action Args
2021-10-29 14:25:28eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, iMath, ohno, mmaswg
2021-10-29 14:25:28eryksunsetmessageid: <>
2021-10-29 14:25:28eryksunlinkissue30082 messages
2021-10-29 14:25:28eryksuncreate