From fba5eb694b0821859719b9ee4e61c36d62eeff20 Mon Sep 17 00:00:00 2001
From: Brian Haley <bhaley@redhat.com>
Date: Wed, 20 Feb 2019 11:44:20 -0500
Subject: Fix pylint R1714 (consider-using-in) refactor messages

Instead of checking variables are equal to one of many
values, use a tuple and check if the variable is 'in' it.
This is faster and less verbose.

Change-Id: I429dbbd92a78fdfae3140cae8a397ff10f6d956e
---
 .pylintrc | 1 -
 1 file changed, 1 deletion(-)

(limited to '.pylintrc')

diff --git a/.pylintrc b/.pylintrc
index dd5c11f8d4..79607cf62f 100644
--- a/.pylintrc
+++ b/.pylintrc
@@ -89,7 +89,6 @@ disable=
 # new for python3 version of pylint
  chained-comparison,
  consider-using-dict-comprehension,
- consider-using-in,
  consider-using-set-comprehension,
  unnecessary-pass,
  useless-object-inheritance
-- 
cgit v1.2.1