From 768c91b58822b41b44203c930d10a6fdc5058674 Mon Sep 17 00:00:00 2001
From: Thomas Wiest <twiest@redhat.com>
Date: Wed, 3 Jun 2015 14:38:10 -0400
Subject: Added 'stylistic exception' to the best practices guide.

---
 docs/best_practices_guide.adoc | 1 +
 1 file changed, 1 insertion(+)

(limited to 'docs/best_practices_guide.adoc')

diff --git a/docs/best_practices_guide.adoc b/docs/best_practices_guide.adoc
index 301c6ccda..af1acd94f 100644
--- a/docs/best_practices_guide.adoc
+++ b/docs/best_practices_guide.adoc
@@ -50,6 +50,7 @@ Instead, http://docs.pylint.org/faq.html#is-it-possible-to-locally-disable-a-par
 .Exceptions:
 1. When PyLint fails because of a dependency that can't be installed on the build bot
 1. When PyLint fails because of including a module that is outside of control (like Ansible)
+1. When PyLint fails, but the code makes more sense the way it is formatted (stylistic exception). For this exception, the description of the PyLint disable MUST state why the code is more clear, AND the person reviewing the PR will decide if they agree or not. The reviewer may reject the PR if they disagree with the reason for the disable.
 
 '''
 [cols="2v,v"]
-- 
cgit v1.2.3

