This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author marco.buttu
Recipients Jim Fasarakis-Hilliard, docs@python, marco.buttu, rhettinger, terry.reedy, wolma
Date 2017-03-01.08:55:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488358506.7.0.0635749815676.issue29414@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't see this point. The other section titles are not about
> loops. The preceding chapter introduces while loops as a loop,
> not a statement, and this chapter talks about while and for
> loops further down the page.

What I mean is that currently in every section (of this chapter) about a statemet, the statement is qualified as "statement": "if Statements", "for Statements", "pass Statements", and "break and continue Statements, and else Clauses on Loops". The last one is not an exeption, bacause we have already introduced for and while, and writing "break and continue Statements, and else Clauses on for and while statements" IMO is redundant. 

I like the current structure of titles, because IMO helps beginners to better classify things (statements, functions, ...), and it is not clear to me the objective motivation for changing "for Statemets" to "for Loops", breaking the structure given by the original author.
History
Date User Action Args
2017-03-01 08:55:06marco.buttusetrecipients: + marco.buttu, rhettinger, terry.reedy, docs@python, wolma, Jim Fasarakis-Hilliard
2017-03-01 08:55:06marco.buttusetmessageid: <1488358506.7.0.0635749815676.issue29414@psf.upfronthosting.co.za>
2017-03-01 08:55:06marco.buttulinkissue29414 messages
2017-03-01 08:55:06marco.buttucreate