Your message dated Tue, 18 Nov 2014 13:08:47 +0100
with message-id <[email protected]>
and subject line Re: Bug#764848: Incorrect behavior of
subprocess.getstatusoutput in python3.4.2
has caused the Debian Bug report #764848,
regarding Incorrect behavior of subprocess.getstatusoutput in python3.4.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
764848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764848
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3.4
Version: 3.4.2~rc1-1
Dear Maintainer,
I recently noticed inconsistent behavior of the function
getstatusoutput from the subprocess module.
According to the help documentation for getstatusoutput the following
should occur in a python3 environment:
>>> import subprocess
>>> subprocess.getstatusoutput('cat /bin/junk')
(256, 'cat: /bin/junk: No such file or directory')
>>>subprocess.getstatusoutput('/bin/junk')
(256, 'sh: /bin/junk: not found')
However, this is what occurs instead:
>>> subprocess.getstatusoutput('cat /bin/junk')
(1, 'cat: /bin/junk: No such file or directory')
>>> subprocess.getstatusoutput('/bin/junk')
(127, '/bin/sh: 1: /bin/junk: not found')
As you can see, the exit status for the 2 calls don't agree with what the
documentation says they should be.
Here's a comparison with python3.2:
>>> import subprocess
>>> subprocess.getstatusoutput('cat /bin/junk')
(256, 'cat: /bin/junk: No such file or directory')
>>> subprocess.getstatusoutput('/bin/junk')
(32512, '/bin/sh: 1: /bin/junk: not found')
It looks to me like the documentation is either wrong, or something has
changed recently with the subprocess module.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python3.4 depends on:
ii libpython3.4-stdlib 3.4.2~rc1-1
ii mime-support 3.57
ii python3.4-minimal 3.4.2~rc1-1
python3.4 recommends no packages.
Versions of packages python3.4 suggests:
ii binutils 2.24.51.20140918-1
ii python3.4-doc 3.4.2~rc1-1
pn python3.4-venv <none>
-- no debconf information
--Rod
--- End Message ---
--- Begin Message ---
On 10/11/2014 05:32 PM, Rod Gomez wrote:
Package: python3.4
Version: 3.4.2~rc1-1
Dear Maintainer,
I recently noticed inconsistent behavior of the function
getstatusoutput from the subprocess module.
According to the help documentation for getstatusoutput the following
should occur in a python3 environment:
import subprocess
subprocess.getstatusoutput('cat /bin/junk')
(256, 'cat: /bin/junk: No such file or directory')
subprocess.getstatusoutput('/bin/junk')
(256, 'sh: /bin/junk: not found')
However, this is what occurs instead:
subprocess.getstatusoutput('cat /bin/junk')
(1, 'cat: /bin/junk: No such file or directory')
subprocess.getstatusoutput('/bin/junk')
(127, '/bin/sh: 1: /bin/junk: not found')
As you can see, the exit status for the 2 calls don't agree with what the
documentation says they should be.
$ python3
Python 3.4.2 (default, Nov 13 2014, 07:01:52)
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.getstatusoutput('ls /bin/ls')
(0, '/bin/ls')
>>> subprocess.getstatusoutput('cat /bin/junk')
(1, 'cat: /bin/junk: No such file or directory')
>>> subprocess.getstatusoutput('/bin/junk')
(127, '/bin/sh: 1: /bin/junk: not found')
>>>
can't see this with 3.4.2-2
--- End Message ---
