disable f-string in logging messages Pylint warning

This is generally considered error prone because you can include non-pure
operations in logging functions that your code accidentally depends on. However
the Graphviz scripts are simple enough that this is not a significant issue. The
use of f-strings pervasively makes for more consistent and readable scripts.

diff --git a/.pylintrc b/.pylintrc
index dd75313373c53d43e8e2befcc2afbfe2db5c25ec..4629b6ee60672887735829ff6e556085861307d2 100644 (file)
--- a/.pylintrc
+++ b/.pylintrc
@@ -141,7 +141,8 @@ disable=print-statement,
         redefined-builtin,
         too-many-branches,
         too-many-statements,
-        too-few-public-methods
+        too-few-public-methods,
+        logging-fstring-interpolation
 
 # Enable the message, report, category or checker with the given id(s). You can
 # either give multiple identifier separated by comma (,) or put this option