GitLab

Conflicts:
	_episodes/02-numpy-backup.md
	_episodes/02-numpy.md
	_episodes/03-matplotlib.md

* Update 04-lists.md

I think it's good to repeat the explanation of behaviour caused by (attempted) copying and then modifying the list in place. From teaching this several times, I think it would help to notify the learner that the use of append here is a second, similar example to what we saw earlier with the salsa list.

* Update 04-lists.md

Replaced brackets with back-ticks and added comma.

* Clarification of 1.0 v 1.

The previous explanation implies that Python will always print 1.0 as "1." when there's nothing after the decimal point. However, this is specific to numpy. For example, the statement "print(1.0)" will print "1.0" and not "1.". I also clarified the space saved was on the screen (rather than in memory for example).

* Update 02-numpy.md

* Update 02-numpy.md

* Update 02-numpy.md

closes #764

* Remove array arithmetic

* Add blank line after heading

The Output block in this exercise contains two assignments to the variable `y`, which neither looks like an Output nor does it follow from the preceding Python block when run.

I believe the first assignment to `y` was intended to be part of the Python block, and I also believe the intent was to print the value of `y`, which is 97, instead of assigning 97 to it in the Output block.

This commit does the following:
- moves the first `y` assignment from the Output block into the Python block
- adds a `print(y)` statement to the end of the Python block
- removes the assignment from the `y = 97` line, so that the Output block matches the output of the edited Python block when it is run.

* Update some docstring sections to use numpy standard.

You will also see that some of the information was incorrect due to
multiple update. The function used to be called `center` and to return
a list instead of a numpy array. So the help and example were incorrect.

The use of the numpy standard is a good practice; as most projects use
it. Even if we don't expect users to remember it; at least they are made
aware that there is standard and can look for it.

This also mirror the documentation style of loadtxt that is seen later
in the lesson.

And finally sphinx can understand numpydoc and generate nice HTML pages.
So all in all I believe this is a nice detail to add to the lesson.

* Use minimal numpy docstring with only example.

I feel that using the word "simple" can be a bit dismissive. I don't think we can assume that novices would agree that the tests outlined would be simple for them to come up with when they're first starting out with Python. I think this can be reworded to convey a similar meaning without being as dismissive.