pylint: upgrade to 1.3.1

pylintrc

Index: pylintrc
===================================================================
--- pylintrc	(revision 292890)
+++ pylintrc	(working copy)
@@ -61,7 +61,10 @@
 # W0603: Using the global statement
 # W0703: Catch "Exception"
 # W1201: Specify string format arguments as logging function parameters
-disable=C0103,C0111,C0302,I0010,I0011,R0801,R0901,R0902,R0903,R0904,R0911,R0912,R0913,R0914,R0915,R0921,R0922,W0122,W0141,W0142,W0402,W0404,W0511,W0603,W0703,W1201
+#
+# These should get enabled, but the codebase has too many violations currently.
+# bad-continuation
+disable=C0103,C0111,C0302,I0010,I0011,R0801,R0901,R0902,R0903,R0904,R0911,R0912,R0913,R0914,R0915,R0921,R0922,W0122,W0141,W0142,W0402,W0404,W0511,W0603,W0703,W1201,bad-continuation

[agable, 2014/11/11 18:08:52]

Please format this with comments so that users know which warnings are being
ignored, and file bugs to fix each class of these warnings at least in the
infrastructure repositories.

I just don't want this to sweep the new warnings under the rug entirely. I'm
fine with disabling the warnings as long as there's an audit trail so people
actually have motivation to go back and fix them in the near future.

[vapier, 2014/11/11 19:50:50]

you've lost me ... there's already a large comment block right above this line
detailing each warning

[agable, 2014/11/12 23:26:57]

Sorry, my bad. Was reviewing too fast and thought the list had substantially
changed while the comment hadn't.

 
 
 [REPORTS]
@@ -70,9 +73,6 @@
 # (visual studio) and html
 output-format=text
 
-# Include message's id in output
-include-ids=yes
-
 # Put messages in a separate file for each module / package specified on the
 # command line instead of printing them on stdout. Reports (if any) will be
 # written in a file name "pylint_global.[txt|html]".