[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

R. David Murray added the comment: The bug doesn't exist on 2.6, so I'm not backporting. Ported to py3k in r76937 and backported to 3.1 in r76938. -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed versions: -Python 2.6

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

R. David Murray added the comment: I has already adjusted the patch, in a slightly different fashion, but to much the same effect. Checked in to trunk in r76935. -- ___ Python tracker _

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Florent Xicluna added the comment: Variant which gives different usage messages: ~ $ ./python -m doctest usage: doctest [-v] file ... ~ $ ./python Lib/doctest.py usage: Lib/doctest.py [-v] file ... -- Added file: http://bugs.python.org/file15626/issue7376_usage_v2.diff __

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

R. David Murray added the comment: The patch results in this type of usage message: usage: /home/rdmurray/python/trunk/Lib/doctest.py [-v] file ... which while technically correct isn't the way I called it. It would be better to at least use basename on argv[0]. (I wonder if there's some way

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by R. David Murray : -- stage: patch review -> commit review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by R. David Murray : -- assignee: -> r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by Florent Xicluna : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Florent Xicluna added the comment: Minor update: replaced '{}' by '{0}' for compatibility with 2.6. Ready for review and merge. -- Added file: http://bugs.python.org/file15622/issue7376_usage.diff ___ Python tracker

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15392/issue7376_usage.diff ___ Python tracker ___ ___ Python-bugs-list ma

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

flox added the comment: Patch could be applied to Python 2.6 and trunk too. -- versions: +Python 2.6, Python 2.7 ___ Python tracker ___ __

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

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

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by flox : Added file: http://bugs.python.org/file15392/issue7376_usage.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

flox added the comment: Patch proposed. -- Added file: http://bugs.python.org/file15391/issue7376_usage.diff ___ Python tracker ___ __

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

flox added the comment: I am ok with the proposal of removing the current "selftest" default behavior. And thank you for the tip. I tried the command "python -m doctest Lib/*.py" and I found interesting things: * #7379 about Lib/fractions.py * #7380 about Lib/uuid.py * #7381 about Lib/subpro

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by R. David Murray : -- title: FAIL: Doctest: __main__.DebugRunner -> "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner ___ Python tracker ___ __