While porting some code from 2.7 to 3.4 I discovered that
command.getstatusoutput() (renamed to subprocess.getstatusoutput() in 3.x)
had changed. Surprise!
The code was working under an earlier version of 3.3 but broke when I ran
it on 3.4. Nowhere was this documented that I could find. Tracking
Documentation (and adding the missing test) sounds right to me.
We'd at least want a versionchanged note on the function itself, and an
entry in the porting section of the (3.3? 3.4?) what's new guide.
Is there anywhere else we might want to mention it?
Regards,
Nick.
Hi,
It looks like new tests are required to check that the behaviour will not
change again.
Victor
Le mardi 24 février 2015, Gregory P. Smith g...@krypto.org a écrit :
While porting some code from 2.7 to 3.4 I discovered that
command.getstatusoutput() (renamed to subprocess.getstatusoutput()
