[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Georg Brandl added the comment: OK, applied in r77086, r77087. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15625/issue7381_py3k_v3.diff ___ Python tracker ___ ___ Python-bugs-list ma

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Florent Xicluna added the comment: Committed to r76925 (trunk) and r76926 (py3k). Thank you Georg. I see small remaining inconsistencies in the docstring. Either we agree with implicit "import subprocess" or "from subprocess import *", but we should not mix both. See additional patches: * is

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Changes by flox : Removed file: http://bugs.python.org/file15446/issue7381.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Changes by flox : Removed file: http://bugs.python.org/file15447/issue7381_py3k.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Changes by flox : Added file: http://bugs.python.org/file15581/issue7381_py3k_v2.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: Patch updated to backport r51536 in trunk. It makes "python -3" happier (do not compare None >= 0). -- Added file: http://bugs.python.org/file15580/issue7381_v2.diff ___ Python tracker _

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Changes by flox : Added file: http://bugs.python.org/file15447/issue7381_py3k.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: Patch against the trunk, and against the Py3k branch. It fixes: * docstring and documentation formatting * and examples -- assignee: -> georg.brandl components: +Documentation nosy: +georg.brandl versions: +Python 2.6, Python 2.7 Added file: http://bugs.pytho

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

Changes by flox : Removed file: http://bugs.python.org/file15386/issue7381_first.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: Forget the "python2.5 -m doctest /usr/lib/python2.5/subprocess.py" in first message msg95625. This command does not do what I guessed. And there's no doctest in the Python2.5 "subprocess" module. The attached patch may be enough to fix the docstring inconsistencies with

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: It may be fixed with "# doctest: +ELLIPSIS" and "# doctest: +SKIP" directives... But it is probably platform-dependent. I have tested only with Debian Lenny. -- ___ Python tracker _

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: I fixed the docstring inconsistency (see patch) and some obvious things. But I still have errors. ~ $ python3 -m doctest py3_failed/subprocess.py ** File "py3_failed/subprocess.py", line 139, in subpro

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

New submission from flox : I've tested the docstring of the module subprocess. Python 2.5 is OK, but Python 3.1 fails. ~ $ python2.5 -m doctest /usr/lib/python2.5/subprocess.py ... -- Ran 15 tests in 0.012s OK ~ $ p