[issue798520] os.popen with invalid mode differs on Windows and POSIX

Mark Lawrence added the comment: Closed as os.popen deprecated in favour of subprocess.popen. -- nosy: +BreamoreBoy resolution: -> wont fix status: open -> closed ___ Python tracker _

[issue798520] os.popen with invalid mode differs on Windows and POSIX

anatoly techtonik added the comment: I can confirm this but, but os.popen() is deprecated in 2.6 hence there is no point in fixing generated exception even though in a language that claims to be cross-platform exceptions should be unified. I would add os.popen to keywords list for future refere

[issue798520] os.popen with invalid mode differs on Windows and POSIX

Amaury Forgeot d'Arc added the comment: On Windows: >>> os.popen("cmd", "") Traceback (most recent call last): File "", line 1, in ValueError: popen() arg 2 must be 'r' or 'w' Windows has a specific implementation of os.popen, which does validate the mode. Whereas on POSIX platforms, the p

[issue798520] os.popen with invalid mode differs on Windows and POSIX

Daniel Diniz added the comment: This snippet still raises 'OSError: [Errno 22] ...' in Linux: import os os.popen('ls', '') Can anyone do a quick check on Windows? -- nosy: +ajaksu2, georg.brandl priority: normal -> low stage: -> test needed versions: +Python 2.7