endolith added the comment:
The fundamental purpose of doctest is to test that examples in documentation
work correctly:
To check that a module’s docstrings are up-to-date by verifying that all
interactive examples still work as documented.
To perform regression testing by verifying
endolith added the comment:
I ran into this bug with sets, too.
Expected:
{6, 5, 3}
Got:
set([5, 3, 6])
Documentation should illustrate how the function is actually meant to be used,
not contrived examples that convert to sorted output purely so that doctest can
understand them
endolith endol...@gmail.com added the comment:
- If the mailbox is written using the mboxrd format and read using the mboxo
format, lines that were meant to start with From are changed to From
. This is a new type of corruption.
Well, yes. So the choices are:
mboxrd as default
New submission from endolith endol...@gmail.com:
Suggestion: Add an option to bin/hex/oct functions to format binary output with
a minimum fixed width, including leading zeros. Also might be useful for hex
and oct.
Currently, bin(18) produces '0b10010'
with this change, something like bin
endolith endol...@gmail.com added the comment:
Ok. I'm not sure what backwards compatibility issues would exist, though.
The only difference is that mboxrd converts
\nFrom → \nFrom
\nFrom → \nFrom
making the conversion reversible, while mboxo does
\nFrom → \nFrom
\nFrom → \nFrom
New submission from endolith endol...@gmail.com:
The documentation states:
Several variations of the mbox format exist to address perceived shortcomings
in the original. In the interest of compatibility, mbox implements the original
format, which is sometimes referred to as mboxo.
http
Changes by endolith endol...@gmail.com:
--
title: Should not use mboxo format - Mailbox module should not use mboxo format
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13698
New submission from endolith [EMAIL PROTECTED]:
One of the principles of Python is that There should be one-- and
preferably only one --obvious way to do it. It seems that the for
line in file idiom is The Way to iterate over the lines of a file, and
older more explicit methods are deprecated
New submission from endolith [EMAIL PROTECTED]:
http://docs.python.org/lib/typecontextmanager.html
if any expection that occurred should be suppressed
--
assignee: georg.brandl
components: Documentation
messages: 71035
nosy: endolith, georg.brandl
severity: normal
status: open
title
