From 63aea7c83b0d3d364d01597828ca06371004eec4 Mon Sep 17 00:00:00 2001 From: Michael Orlitzky Date: Sun, 13 Nov 2016 16:26:47 -0500 Subject: [PATCH] Disable all variable/method name warnings from pylint. Ain't nobody got time for this. --- .pylintrc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/.pylintrc b/.pylintrc index 47881da..82f5586 100644 --- a/.pylintrc +++ b/.pylintrc @@ -7,8 +7,13 @@ jobs=2 [MESSAGES CONTROL] # Thanks, but you don't need to tell me that I suppressed the message -# that I suppressed. Kinda defeats the point, eh? -disable=I0011,I0020 +# that I suppressed. Kinda defeats the point, eh? Those are the "I" +# rules. +# +# The "C0103" rule is for my variable names, all of which come from +# mathematical references and would be more confusing if I changed them +# for no reason in the source code. +disable=I0011,I0020,C0103 [REPORTS] reports=no @@ -17,11 +22,6 @@ reports=no # Allow map() and filter() functions, because why the fuck not? bad-functions= -# These are all names from the associated papers. It would be more -# confusing to name them something else and then have to juggle them -# in your head as you switch between the source code and the papers. -good-names=a,b,_b,_c,D,e1,e2,_G,_h,A,_A,_C,G,H,K,_K,L,_L,indented_L,M - # A regular expression matching correct method names. This differs # from the default in that it will accept much longer names (50 # characters) if they happen to begin with "test_". -- 2.43.2