Author terry.reedy
Recipients georg.brandl, terry.reedy
Date 2008-12-08.23:05:48
SpamBayes Score 9.03307e-08
Marked as misclassified No
Message-id <1228777550.97.0.72005547671.issue4603@psf.upfronthosting.co.za>
In-reply-to
Content
In 2.6, Ref Manual / Lexical Analysis / Indentation says

"First, tabs are replaced (from left to right) by one to eight spaces
such that the total number of characters up to and including the
replacement is a multiple of eight (this is intended to be the same rule
as used by Unix). The total number of spaces preceding the first
non-blank character then determines the line’s indentation. "

and Using Python / Command line / Misc options says

"-t
    Issue a warning when a source file mixes tabs and spaces for
indentation in a way that makes it depend on the worth of a tab
expressed in spaces. Issue an error when the option is given twice (-tt)."

Inyeol Lee, on c.l.p., in response to a report of a TabError, says "-tt
option in python 2.x is now default in python 3.0.
Apparently it got slipped from any documentation, including what's
new."

In 3.0 docs, the -t option *was* removed from Using Python, but the
Indentation sentences quoted above remain unchanged, though obsolete.  I
would guess that they should be replaced by something like

"When a source file mixes tabs and spaces for indentation in a way that
makes it depend on the worth of a tab expressed in spaces, a TabError is
raised." 

Perhaps What's New should get a sentence too.  "The former -tt startup
option to raise TabError on ambiguous mixtures of tabs and spaces for
indentation has been removed as an option and is now the standard behavior."
History
Date User Action Args
2008-12-08 23:05:51terry.reedysetrecipients: + terry.reedy, georg.brandl
2008-12-08 23:05:51terry.reedysetmessageid: <1228777550.97.0.72005547671.issue4603@psf.upfronthosting.co.za>
2008-12-08 23:05:50terry.reedylinkissue4603 messages
2008-12-08 23:05:48terry.reedycreate