R. David Murray added the comment:
In the absence of feedback about the doc patch, I have applied it in r81634.
@techtonic: if I recall correctly I explained in your issue that had the patch
what the problem was. Short summary: there are two equally valid ways in which
tabs in the output and
anatoly techtonik added the comment:
Sorry for not being able to follow up on this issue. I believe we need to
expand the problem of handling tabs in doctests with use cases and expose the
problem outside the issue tracker item. I still remember that at some point I
had a patch somewhere that
R. David Murray added the comment:
I tried your suggestion, but it seemed to me that it made the first paragraph
of that section be all about tabs, and get even farther away from its original
focus, which was introducing the example.
I've attached a patch that instead moves the entire discuss
Rodrigo Bernardo Pimentel added the comment:
I've just been bitten by this, and I agree the language in the docs is very
inappropriate (made me angry for a minute :)).
One suggestion: "While not everyone might believe tabs should mean that,
doctests are primarily aimed at documentation, and,
R. David Murray added the comment:
The problem is that it would be equally reasonable for someone to want to put
real tab characters in the output section (which results in strange looking
doctest text) or to put expanded spaces in the doctest output section based on
the assumption that outpu
