@@ -11,7 +11,7 @@ contributor.
1111Following the simple guidelines below makes it easier to review and integrate
1212your changes:
1313
14- * ` PEP 8 `_ , the Python style guide, should be followed where possible
14+ * :pep: ` 8 ` , the Python style guide, should be followed where possible
1515* Adding documentation for new methods and classes is very important
1616* Testing your changes with multiple Python versions is fantastically useful, it
1717 is all too easy to use functionality that exists in only specific Python
3333 patches to increase test coverage are greatly appreciated
3434
3535The preferred way to run the package's tests is with :pypi: `nose `.
36- ``nosetests `` provides excellent reporting options and its additional features
37- make it invaluable, see the nose _ documentation for usage information.
36+ ``nosetests ``, nose's command-line test runner, provides excellent reporting
37+ options and its additional features make it invaluable, see the nose _
38+ documentation for usage information.
3839
3940There is a :pypi: `tox ` configuration file included in the repository, you can
4041use it to run the tests against multiple Python versions with a single command.
@@ -79,7 +80,6 @@ unfortunately can't be used.
7980 likely to be comfortable with these already
8081
8182.. _GitHub : https://github.com/ask/python-github2/
82- .. _PEP 8 : http://www.python.org/dev/peps/pep-0008/
8383.. _Sphinx : http://sphinx.pocoo.org/
8484.. _autodoc : http://sphinx.pocoo.org/ext/autodoc.html#module-sphinx.ext.autodoc
8585.. _nose : http://somethingaboutorange.com/mrl/projects/nose/
0 commit comments