The tutorial code for Continue at https://docs.python.org/3.7/tutorial/controlflow.html#break-and-continue-statements-and-else-clauses-on-loops is missing a
...
null statement.

Actual code/result:

>>> for num in range(2, 10):
...     if num % 2 == 0:
...         print("Found an even number", num)
...         continue
...     print("Found a number", num)
Found an even number 2
Found a number 3
Found an even number 4
Found a number 5
Found an even number 6
Found a number 7
Found an even number 8
Found a number 9

Expected code/result:

>>> for num in range(2, 10):
...     if num % 2 == 0:
...         print("Found an even number", num)
...         continue
...     print("Found a number", num)
...
Found an even number 2
Found a number 3
Found an even number 4
Found a number 5
Found an even number 6
Found a number 7
Found an even number 8
Found a number 9

I think the ommission of secondary prompt(...) at the end of the loop in the code snippet doesn't affect what the example wanted to demonstrate. Even so, if this has to be fixed, this correction is to be done in versions 3.5 through 3.10

@docorbit@sonic.net are you going to submit a PR for it or am I free to do it?

Um, Python newcomer here. What's a PR? Pull request?

I'm happy to do it if you can point me to the how-to. I know my way around git, and not around Python community standards. 

You are also welcome to go ahead and make the change; thank you for asking.

Please go head @docorbit@sonic.net! It's a good one to get familiar with the process of contributing. Yes, PR stands for Pull Request.

There is the devguide (https://devguide.python.org/), which documents how to contribute. In fact, the quick guide may be sufficient. Feel free to ask any further questions, I'm eager to help!

@DahlitzFlorian: I'm happy do to the PR provided I don't actually have to build Python to work on a documentation change. If it does require building Python then please go ahead.

That said, I've looked at the Doc/tutorial/controlflow.rst and it appears to be a plain text file. I believe that I would have a PR up by May 26, 2020. Is the best practice to check out the 3.10 branch then add backport tags for the other versions to the PR? That wasn't clear to me from the docs you referred me to.

I pointed you to the quick guide. In fact, you fork the cpython repository, create a new branch called fix-issue-40640, change the file Doc/tutorial/controlflow.rst and submit a PR agains the cpython master branch. As Rahul as already added all the versions to the issue that need a backport, the cpython bot will handle it for you. So you only need to submit a PR to the master branch. :)

@Florian Dahlitz, thank you for your help. I have created a PR at https://github.com/python/cpython/pull/20334 and it is awaiting approval of my CLA and of the change itself.

ping

Chas - there is a conflict in the PR. Would you mind refreshing it? I'll try to make sure it gets merged this time.

New changeset 48cb11bf5b426bd3f1d010f987c03115661261b7 by Miss Islington (bot) in branch '3.10':
bpo-40640: doc -- add missing ... in example of Continue (GH-26055) (GH-26057)
https://github.com/python/cpython/commit/48cb11bf5b426bd3f1d010f987c03115661261b7

New changeset ada9cdb94158a101db65af17b62cdd2ae6c3e782 by Miss Islington (bot) in branch '3.9':
bpo-40640: doc -- add missing ... in example of Continue (GH-26055) (GH-26058)
https://github.com/python/cpython/commit/ada9cdb94158a101db65af17b62cdd2ae6c3e782

Thank you Chas!