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.

classification
Title: Results in section 4.4 break and continue
Type: Stage: resolved
Components: Documentation Versions: Python 3.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Lisabel Leon, docs@python, matrixise, zach.ware
Priority: normal Keywords:

Created on 2017-07-25 15:15 by Lisabel Leon, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
testresults.PNG Lisabel Leon, 2017-07-25 15:15 My results
Messages (5)
msg299097 - (view) Author: Lisabel Leon (Lisabel Leon) Date: 2017-07-25 15:15
The first example of this section shows different results if typed into the Python interpreter.  This is the documentation (documentation.png) and these are the results as I type it into my environment (testresults.jpg).
msg299099 - (view) Author: Stéphane Wirtel (matrixise) * (Python committer) Date: 2017-07-25 15:16
could you be more explicit? which section ?

Thank you
msg299116 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2017-07-25 15:56
Take a look at the statement immediately following the example:

"(Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.)"

The example is correct, and is introducing the concept of an 'else' clause on a for loop.  This is very much not the first report of this that we've had, though; perhaps the 'look closely' admonition should be moved before the example?

For future reference, please copy and paste the text of your tests rather than a screenshot; not all participants can see the screenshot.
msg299117 - (view) Author: Lisabel Leon (Lisabel Leon) Date: 2017-07-25 16:04
Thank you Zachary for such a speedy response.
I'll paste text next time.

Rgds!
Lisabel

On Tue, Jul 25, 2017 at 11:56 AM, Zachary Ware <report@bugs.python.org>
wrote:

>
> Zachary Ware added the comment:
>
> Take a look at the statement immediately following the example:
>
> "(Yes, this is the correct code. Look closely: the else clause belongs to
> the for loop, not the if statement.)"
>
> The example is correct, and is introducing the concept of an 'else' clause
> on a for loop.  This is very much not the first report of this that we've
> had, though; perhaps the 'look closely' admonition should be moved before
> the example?
>
> For future reference, please copy and paste the text of your tests rather
> than a screenshot; not all participants can see the screenshot.
>
> ----------
> nosy: +zach.ware
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue31037>
> _______________________________________
>
msg299288 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2017-07-27 02:53
We just received another report about this on docs@:

https://mail.python.org/pipermail/docs/2017-July/032314.html
History
Date User Action Args
2022-04-11 14:58:49adminsetgithub: 75220
2017-07-27 02:53:36zach.waresetmessages: + msg299288
2017-07-26 06:26:47rhettingersetstatus: open -> closed
resolution: not a bug
stage: resolved
2017-07-25 16:04:20Lisabel Leonsetmessages: + msg299117
2017-07-25 15:56:15zach.waresetnosy: + zach.ware
messages: + msg299116
2017-07-25 15:16:32matrixisesetnosy: + matrixise
messages: + msg299099
2017-07-25 15:15:09Lisabel Leoncreate