Mention some possible errors in the python intro (DjangoGirls#933)

MatMoore · helenst · commit 97f8311f7b3c · 2016-12-23T08:53:37.000Z
* Mention some possible errors in the python intro When showing how to define a function, mention some things that can go wrong, instead of saying "that was easy" From @vrutkovs suggestion in issue DjangoGirls#196: > People usually read the chapter line by line and get confused that > things break (on such an early stage). The coach has to know this > situation in beforehand and warn the student (I almost filed a bug about > incorrect syntax in the example) * Improve information about things that can go wrong - Use a list to make this section more distinct - Mention what happens if you indent the function call itself
diff --git a/en/python_introduction/README.md b/en/python_introduction/README.md
@@ -793,7 +793,12 @@ Hi there!
 How are you?
 ```
 
-That was easy! Let's build our first function with parameters. We will use the previous example – a function that says 'hi' to the person running it – with a name:
+Note: if it didn't work, don't panic! The output will help you to figure why:
+- If you get a `NameError`, that probably means you typed something wrong, so you should check that you used the same name when creating the function with `def hi():` and when calling it with `hi()`.
+- If you get an `IndentationError`, check that both of the `print` lines have the same whitespace at the start of a line: python wants all the code inside the function to be neatly aligned.
+- If there's no output at all, check that the last `hi()` *isn't* indented - if it is, that line will become part of the function too, and it will never get run.
+
+Let's build our first function with parameters. We will use the previous example – a function that says 'hi' to the person running it – with a name:
 
 {% filename %}python_intro.py{% endfilename %}
 ```python
