Add references.

kaycebasques · kaycebasques · commit 83e078216301 · 2014-10-15T19:05:15.000-07:00
diff --git a/docs/correctness/assigning_to_function_call_which_only_returns_none.rst b/docs/correctness/assigning_to_function_call_which_only_returns_none.rst
@@ -66,3 +66,4 @@ To achieve the desired result of printing "hello" to the screen, the ``hello`` f
 References
 ----------
 - `Stack Overflow - Assigning a function to a variable <http://stackoverflow.com/questions/10354163/assigning-a-function-to-a-variable>`_
+- `PyLint - W1111 <http://pylint-messages.wikidot.com/messages:w1111>`_
diff --git a/docs/correctness/do_not_assign_a_lambda_expression.rst b/docs/correctness/do_not_assign_a_lambda_expression.rst
@@ -53,4 +53,4 @@ References
 ----------
 - `PEP 8 Style Guide - Programming Recommendations <http://legacy.python.org/dev/peps/pep-0008/#programming-recommendations>`_
 - `Stack Overflow - Do not assign a lambda expression <http://stackoverflow.com/questions/25010167/e731-do-not-assign-a-lambda-expression-use-a-def>`_
-
+- pep8 - E731
diff --git a/docs/correctness/indentation_contains_mixed_spaces_and_tabs.rst b/docs/correctness/indentation_contains_mixed_spaces_and_tabs.rst
@@ -48,3 +48,4 @@ References
 ----------
 - `PEP 8 Style Guide - Tabs or Spaces? <http://legacy.python.org/dev/peps/pep-0008/#tabs-or-spaces>`_
 - `PEP 8 Style Guide - Indentation <http://legacy.python.org/dev/peps/pep-0008/#indentation>`_
+- pep8 - E731
diff --git a/docs/correctness/indentation_contains_tabs.rst b/docs/correctness/indentation_contains_tabs.rst
@@ -48,3 +48,4 @@ References
 ----------
 - `PEP 8 Style Guide - Tabs or Spaces? <http://legacy.python.org/dev/peps/pep-0008/#tabs-or-spaces>`_
 - `PEP 8 Style Guide - Indentation <http://legacy.python.org/dev/peps/pep-0008/#indentation>`_
+- pep8 - W191
diff --git a/docs/correctness/iter_returns_non-iterator.rst b/docs/correctness/iter_returns_non-iterator.rst
@@ -75,3 +75,4 @@ References
 - `The Python Tutorial - Iterators <https://docs.python.org/3/tutorial/classes.html#iterators>`_
 - `The Python Language Reference - Iterator Types <https://docs.python.org/2/library/stdtypes.html#iterator-types>`_
 - `Stack Overflow - Understanding Python's Iterator, Iterable, and Iteration Protocols <http://stackoverflow.com/questions/9884132/understanding-pythons-iterator-iterable-and-iteration-protocols-what-exact>`_
+- PyLint - W0234
diff --git a/docs/maintainability/duplicate_key_in_dictionary.rst b/docs/maintainability/duplicate_key_in_dictionary.rst
@@ -41,3 +41,4 @@ In the modified module below the second, duplicate entry for ``gmt`` has been de
 
 References
 ----------
+- PyLint - W0109
diff --git a/docs/maintainability/from_module_import_all_used.rst b/docs/maintainability/from_module_import_all_used.rst
@@ -41,3 +41,5 @@ The ``import`` statement should be refactored to be more specific about what fun
 References
 ----------
 - `Stack Overflow - Importing Modules <http://stackoverflow.com/questions/15145159/importing-modules-how-much-is-too-much>`_
+- PyFlakes - F403
+
diff --git a/docs/maintainability/import_module_shadowed_by_loop_variable.rst b/docs/maintainability/import_module_shadowed_by_loop_variable.rst
@@ -53,3 +53,4 @@ A for loop variable should never use the name of an imported module. In the modi
     
 References
 ----------
+- Pyflakes - F402
diff --git a/docs/maintainability/local_variable_name_is_assigned_to_but_never_used.rst b/docs/maintainability/local_variable_name_is_assigned_to_but_never_used.rst
@@ -58,3 +58,4 @@ If the variable is a reminder of some part of the function that still needs to b
 
 References
 ----------
+- Pyflakes - F841
diff --git a/docs/maintainability/module_imported_but_not_used.rst b/docs/maintainability/module_imported_but_not_used.rst
@@ -59,3 +59,4 @@ In the modified version of the module below, the module now uses ``math.floor``
     
 References
 ----------
+- Pyflakes - F401
diff --git a/docs/maintainability/not_enough_arguments_for_format_string.rst b/docs/maintainability/not_enough_arguments_for_format_string.rst
@@ -51,3 +51,4 @@ The modified module below adds a second argument to ``format()``.
 
 References
 ----------
+- PyLint - E1306
diff --git a/docs/maintainability/redefining_built-in.rst b/docs/maintainability/redefining_built-in.rst
@@ -1,5 +1,5 @@
 Redefining built-in %r
-=================
+======================
 
 Summary
 -------
@@ -71,4 +71,4 @@ Explicitly reference each function by module.
 References
 ----------
 - `Stack Overflow - Module name redefines built-in <http://stackoverflow.com/questions/3639511/module-name-redefines-built-in>`_
-
+- PyLint - W0622
diff --git a/docs/maintainability/redefinition_of_unused_name.rst b/docs/maintainability/redefinition_of_unused_name.rst
@@ -61,3 +61,4 @@ Another way to suppress the ``redefinition of unused name`` error is to remove t
 
 References
 ----------
+- Pyflakes - F811
diff --git a/docs/maintainability/too_many_arguments_for_format_string.rst b/docs/maintainability/too_many_arguments_for_format_string.rst
@@ -51,3 +51,4 @@ The modified module below adds another replacement field to the string literal t
 
 References
 ----------
+- PyLint - E1305
diff --git a/docs/maintainability/undefined_name_in_all.rst b/docs/maintainability/undefined_name_in_all.rst
@@ -61,3 +61,4 @@ If the object is private (meaning it should not be listed in ``__all__`` or if t
 References
 ----------
 - `Stack Overflow - Can someone explain __all__ in Python? <http://stackoverflow.com/questions/44834/can-someone-explain-all-in-python>`_
+- Pyflakes - F822
diff --git a/docs/maintainability/unused_import.rst b/docs/maintainability/unused_import.rst
@@ -56,3 +56,4 @@ Upon reviewing the module, the author realized that he forgot to implement a por
 
 References
 ----------
+- PyLint - W0611
diff --git a/docs/maintainability/unused_import_from_wildcard_import.rst b/docs/maintainability/unused_import_from_wildcard_import.rst
@@ -44,3 +44,4 @@ The modified module below has replaced the wildcard import with explicit imports
 References
 ----------
 - `PEP 20 - The Zen of Python <http://legacy.python.org/dev/peps/pep-0020/>`_
+- PyLint - W0614
diff --git a/docs/maintainability/unused_variable.rst b/docs/maintainability/unused_variable.rst
@@ -60,3 +60,4 @@ After receiving the ``unused variable`` error the author reviews the section of
     
 References
 ----------
+- PyLint - W0612
diff --git a/docs/maintainability/using_possible_undefined_loop_variable.rst b/docs/maintainability/using_possible_undefined_loop_variable.rst
@@ -47,3 +47,4 @@ The modified module below indents the statement ``s.append(n)`` to clarify that
 
 References
 ----------
+- PyLint - W0631
diff --git a/docs/maintainability/using_the_global_statement.rst b/docs/maintainability/using_the_global_statement.rst
@@ -77,3 +77,4 @@ One common solution for avoiding global variables is to create a class and store
 References
 ----------
 - `Cunningham & Cunningham, Inc. - Global Variables Are Bad <http://c2.com/cgi/wiki?GlobalVariablesAreBad>`_
+- PyLint - W0603
diff --git a/docs/maintainability/wildcard_import.rst b/docs/maintainability/wildcard_import.rst
@@ -55,3 +55,4 @@ References
 ----------
 - `Stack Overflow - Should wildcard import be avoided? <http://stackoverflow.com/questions/3615125/should-wildcard-import-be-avoided>`_
 - `PEP8 Style Guide - Imports <http://legacy.python.org/dev/peps/pep-0008/#imports>`_
+- PyLint - W0401
diff --git a/docs/readability/comparison_to_none.rst b/docs/readability/comparison_to_none.rst
@@ -48,3 +48,4 @@ The code below refactors the comparison to ``None`` to use the PEP 8 preferred p
 References
 ----------
 - `PEP 8 Style Guide - Progrmaming Recommendations <http://legacy.python.org/dev/peps/pep-0008/#programming-recommendations>`_
+- pep8 - E711
diff --git a/docs/readability/comparison_to_true.rst b/docs/readability/comparison_to_true.rst
@@ -59,3 +59,4 @@ The code below refactors the comparison to ``True`` to use the PEP 8 preferred p
 References
 ----------
 - `PEP 8 Style Guide - Progrmaming Recommendations <http://legacy.python.org/dev/peps/pep-0008/#programming-recommendations>`_
+- pep8 - E712
diff --git a/docs/readability/do_not_compare_types_use_isinstance.rst b/docs/readability/do_not_compare_types_use_isinstance.rst
@@ -81,3 +81,4 @@ The preferred pattern for comparing types is the built-in function ``isinstance`
 References
 ----------
 - `Stack Overflow: Differences between isinstance() and type() in Python <http://stackoverflow.com/questions/1549801/differences-between-isinstance-and-type-in-python>`_
+- pep8 - E721
diff --git a/docs/readability/lambda_may_not_be_necessary.rst b/docs/readability/lambda_may_not_be_necessary.rst
@@ -47,4 +47,5 @@ The modified module below has removed the unnecessary lambda and just calls the
     
 References
 ----------
+- PyLint - W0108
 - `Oliver Fromme <http://www.secnetix.de/olli/Python/lambda_functions.hawk>`_
diff --git a/docs/readability/test_for_membership_should_be_not_in.rst b/docs/readability/test_for_membership_should_be_not_in.rst
@@ -53,3 +53,4 @@ References
 ----------
 - `PEP8 Style Guide - Programming Recommendations <http://legacy.python.org/dev/peps/pep-0008/#programming-recommendations>`_
 - `Stack Overflow - What is more 'pythonic' for 'not'? <http://stackoverflow.com/questions/17659303/what-is-more-pythonic-for-not>`_
+- pep8 - E713
diff --git a/docs/readability/test_for_object_identity_should_be_is_not.rst b/docs/readability/test_for_object_identity_should_be_is_not.rst
@@ -42,3 +42,4 @@ Refactor the statement to the more readable ``OBJECT is not CLASS`` pattern.
 References
 ----------
 - `PEP8 Style Guide - Programming Recommendations <http://legacy.python.org/dev/peps/pep-0008/#programming-recommendations>`_
+- pep8 - E714
diff --git a/docs/readability/unnecessary_pass_statement.rst b/docs/readability/unnecessary_pass_statement.rst
@@ -42,5 +42,5 @@ Removing the ``pass`` statement suppresses the ``Unnecessary pass statement`` er
 
 References
 ----------
-- `PyLint <http://pylint-messages.wikidot.com/messages:w0107>`_
+- `PyLint - W0107 <http://pylint-messages.wikidot.com/messages:w0107>`_
 - `Python Language Reference <https://docs.python.org/3/reference/simple_stmts.html#the-pass-statement>`_
diff --git a/docs/readability/use_new_raise_syntax.rst b/docs/readability/use_new_raise_syntax.rst
@@ -48,3 +48,4 @@ The updated module has replaced the old style ``raise`` statement ``raise Except
 References
 ----------
 - `PEP 3109 - Raising Exceptions in Python 3 <http://legacy.python.org/dev/peps/pep-3109/>`_
+- PyLint - W0121
diff --git a/docs/readability/using_map_or_filter_where_list_comprehension_is_possible.rst b/docs/readability/using_map_or_filter_where_list_comprehension_is_possible.rst
@@ -42,3 +42,4 @@ In the modified module below, the module uses a list comprehension to generate t
 References
 ----------
 `Oliver Fromme - List Comprehensions <http://www.secnetix.de/olli/Python/list_comprehensions.hawk>`_
+- PyLint - W0110
diff --git a/docs/security/use_of_exec.rst b/docs/security/use_of_exec.rst
@@ -41,6 +41,6 @@ In most scenarios, you can easily refactor the code to avoid the use of ``exec``
 
 References
 ----------
-- `PyLint - Use of exec <http://pylint-messages.wikidot.com/messages:w0122>`_
+- `PyLint - W0122 <http://pylint-messages.wikidot.com/messages:w0122>`_
 - `Python Language Reference - The exec statement <https://docs.python.org/2/reference/simple_stmts.html#the-exec-statement>`_
 - `Stack Overflow - Why should exec() and eval() be avoided? <http://stackoverflow.com/questions/1933451/why-should-exec-and-eval-be-avoided>`_

Original file line number	Diff line number	Diff line change
@@ -41,3 +41,4 @@ In the modified module below the second, duplicate entry for ``gmt`` has been de
`41`	`41`
`42`	`42`	`References`
`43`	`43`	`----------`
	`44`	`+- PyLint - W0109`
Original file line number	Diff line number	Diff line change
`@@ -53,3 +53,4 @@ A for loop variable should never use the name of an imported module. In the modi`
`53`	`53`
`54`	`54`	`References`
`55`	`55`	`----------`
	`56`	`+- Pyflakes - F402`
Original file line number	Diff line number	Diff line change
`@@ -58,3 +58,4 @@ If the variable is a reminder of some part of the function that still needs to b`
`58`	`58`
`59`	`59`	`References`
`60`	`60`	`----------`
	`61`	`+- Pyflakes - F841`
Original file line number	Diff line number	Diff line change
@@ -59,3 +59,4 @@ In the modified version of the module below, the module now uses ``math.floor``
`59`	`59`
`60`	`60`	`References`
`61`	`61`	`----------`
	`62`	`+- Pyflakes - F401`