change recommended max line length to 120 and rewrap the doc itself accordingly

Author: gdementen

doc/source/contribute.rst

@@ -6,13 +6,10 @@ Getting the code (for the first time)
 
 - install a Git client
 
-  On Windows, TortoiseGit provides a nice graphical wrapper. You need to
-  install both the console client from http://msysgit.github.io/ and
-  `TortoiseGit <https://code.google.com/p/tortoisegit>`_
-  itself.
+  On Windows, TortoiseGit provides a nice graphical wrapper. You need to install both the console client from
+  http://msysgit.github.io/ and `TortoiseGit <https://code.google.com/p/tortoisegit>`_ itself.
 
-- create an account on `GitHub <https://github.com/>`_ (not necessary for
-  readonly).
+- create an account on `GitHub <https://github.com/>`_ (not necessary for readonly).
 
 - clone the repository on your local machine ::
 
@@ -26,14 +23,13 @@ You could install LArray in the standard way: ::
 
   > python setup.py install
 
-but in that case you need to "install" it again every time you change it. When
-developing, it is usually more convenient to use: ::
+but in that case you need to "install" it again every time you change it. When developing, it is usually more
+convenient to use: ::
 
   > python setup.py develop
 
-This creates some kind of symlink between your python installation "modules"
-directory and your repository, so that any change in your local copy is
-automatically usable by other modules.
+This creates some kind of symlink between your python installation "modules" directory and your repository, so that any
+change in your local copy is automatically usable by other modules.
 
 
 Updating your local copy with remote changes
@@ -47,13 +43,11 @@ Updating your local copy with remote changes
 Code conventions
 ----------------
 
-`PEP8 <http://www.python.org/dev/peps/pep-0008/>`_ is your friend. Among others,
-this means:
+`PEP8 <http://www.python.org/dev/peps/pep-0008/>`_ is your friend. Among others, this means:
 
-- 80 characters lines
+- 120 characters lines
 - 4 spaces indentation
-- lowercase (with underscores if needed) variables, functions, methods and
-  modules names
+- lowercase (with underscores if needed) variables, functions, methods and modules names
 - CamelCase classes names
 - all uppercase constants names
 - whitespace around binary operators
@@ -92,7 +86,7 @@ We use Numpy conventions for docstrings. Here is a template: ::
 
       Returns
       -------
-      name : type
+      type
           Description of return value.
 
       See Also
@@ -119,9 +113,8 @@ For example: ::
 
       Returns
       -------
-      result : bool
-          Whether the string representation of the number is equal to the
-          string.
+      bool
+          Whether the string representation of the number is equal to the string.
 
       Examples
       --------
@@ -138,21 +131,18 @@ For example: ::
 Documentation
 -------------
 
-The documentation is written using reStructuredText and built to various
-formats using `Sphinx <http://sphinx-doc.org/>`_. See the `reStructuredText
-Primer <http://sphinx-doc.org/rest.html#rst-primer>`_ for a first introduction
-of the syntax.
+The documentation is written using reStructuredText and built to various formats using
+`Sphinx <http://sphinx-doc.org/>`_. See the `reStructuredText Primer <http://sphinx-doc.org/rest.html#rst-primer>`_
+for a first introduction of the syntax.
 
 Installing Requirements
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-Basic requirements (to generate an .html version of the documentation) can be
-installed using: ::
+Basic requirements (to generate an .html version of the documentation) can be installed using: ::
 
   > conda install sphinx numpydoc
 
-To build the .pdf version, you need a LaTeX processor. We use
-`MiKTeX <http://miktex.org>`_.
+To build the .pdf version, you need a LaTeX processor. We use `MiKTeX <http://miktex.org>`_.
 
 To build the .chm version, you need `HTML Help Workshop
 <http://www.microsoft.com/en-us/download/details.aspx?id=21138>`_.
@@ -165,27 +155,26 @@ Open a command prompt and go to the documentation directory: ::
 
   > cd doc
 
-If you just want to check that there is no syntax error in the documentation
-and that it formats properly, it is usually enough to only generate the .html
-version, by using: ::
+If you just want to check that there is no syntax error in the documentation and that it formats properly, it is
+usually enough to only generate the .html version, by using: ::
 
   > make html
 
 Open the result in your favourite web browser. It is located in: ::
 
   build/html/index.html
 
-If you want to also generate the .pdf and .chm (and you have the extra
-requirements to generate those), you could use: ::
+If you want to also generate the .pdf and .chm (and you have the extra requirements to generate those), you could
+use: ::
 
   > buildall
 
 
 Tests
 -----
 
-We use both unit tests and doctests. Unit tests are written using Python's
-built-in `unittest module <https://docs.python.org/3/library/unittest.html>`_.
+We use both unit tests and doctests. Unit tests are written using Python's built-in
+`unittest module <https://docs.python.org/3/library/unittest.html>`_.
 For example: ::
 
   from unittest import TestCase
@@ -205,12 +194,10 @@ To run all unit tests: ::
 
   > python -m unittest -v larray\tests\test_la.py
 
-We also use doctests for some tests. Doctests is specially-formatted code
-within the docstring of a function which embeds the result of calling said
-function with a particular set of arguments. This can be used both as
-documentation and testing. We only use doctests for the cases where the test is
-simple enough to fit on one line and it can help understand what the function
-does. For example: ::
+We also use doctests for some tests. Doctests is specially-formatted code within the docstring of a function which
+embeds the result of calling said function with a particular set of arguments. This can be used both as documentation
+and testing. We only use doctests for the cases where the test is simple enough to fit on one line and it can help
+understand what the function does. For example: ::
 
   def slice_to_str(key):
       """Converts a slice to a string
@@ -225,8 +212,7 @@ To run doc tests: ::
 
   > python -m doctest -v larray\larray.py
 
-To run both at the same time, one can use nosetests (install with `conda
-install nose`): ::
+To run both at the same time, one can use nosetests (install with `conda install nose`): ::
 
   > nosetests -v --with-doctest
 
@@ -236,11 +222,9 @@ Sending your changes
 
 ::
 
-  > git add       # tell git it should care about a file it previously
-                  # ignored (only if needed)
+  > git add       # tell git it should care about a file it previously ignored (only if needed)
 
-  > git commit    # creates a new revision of the repository using its
-                  # current state
+  > git commit    # creates a new revision of the repository using its current state
 
   > git pull      # updates your local repository with "upstream" changes.
                   # this might create conflicts that you will need to resolve.