Message229355
It probably comes from this change:
---
changeset: 86879:c34e163c0086
branch: 3.3
parent: 86870:dbff708e393f
user: Tim Golden <mail@timgolden.me.uk>
date: Sun Nov 03 12:53:17 2013 +0000
files: Lib/subprocess.py Lib/test/test_subprocess.py Misc/NEWS
description:
Issue #10197 Rework subprocess.get[status]output to use subprocess functionality and thus to work on Windows. Patch by Nick Coghlan.
---
> (U) This is a breaking change for code relying on what was already a legacy interface.
CommandTests.test_getoutput() only checks that an error returns a non-zero status :-/ It doens't check for the exact status. We should use a small Python program using a specific exit code (ex: sys.exit(5)) to check the status. |
|
Date |
User |
Action |
Args |
2014-10-14 21:14:25 | vstinner | set | recipients:
+ vstinner, ncoghlan, tim.golden, josh.r |
2014-10-14 21:14:25 | vstinner | set | messageid: <1413321265.77.0.775008798711.issue22635@psf.upfronthosting.co.za> |
2014-10-14 21:14:25 | vstinner | link | issue22635 messages |
2014-10-14 21:14:25 | vstinner | create | |
|