summaryrefslogtreecommitdiff
path: root/doc/whatsnew/2.2.rst
diff options
context:
space:
mode:
authorClaudiu Popa <pcmanticore@gmail.com>2018-11-28 09:13:17 +0100
committerClaudiu Popa <pcmanticore@gmail.com>2018-11-28 09:17:20 +0100
commit754ce1dffae4c8e5a1f40decc24ebf03024ab97d (patch)
tree575c20c638f44867d34a0a24fb93fb819243cf8a /doc/whatsnew/2.2.rst
parent484d1720a177454ca783d526c9a55b85c3516016 (diff)
downloadpylint-git-754ce1dffae4c8e5a1f40decc24ebf03024ab97d.tar.gz
Change the ``logging-format-style`` to use name identifier instead of their corresponding Python identifiers
This is to prevent users having to think about escaping the default value for ``logging-format-style`` in the generated config file. Also our config parsing utilities don't quite support escaped values when it comes to ``choices`` detection, so this would have needed various hacks around that. Close #2614
Diffstat (limited to 'doc/whatsnew/2.2.rst')
-rw-r--r--doc/whatsnew/2.2.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/whatsnew/2.2.rst b/doc/whatsnew/2.2.rst
index b33d60945..b61a43fd7 100644
--- a/doc/whatsnew/2.2.rst
+++ b/doc/whatsnew/2.2.rst
@@ -20,6 +20,9 @@ New checkers
* ``logging-format-style`` is a new option for the logging checker for usage of
str.format() style format strings in calls to loggers.
+ It accepts two options: ``--logging-format-style=old`` for using `%` style formatting,
+ which is the assumed default, and ``--logging-format-style=new`` for using `{}` style formatting.
+
* ``implicit-str-concat-in-sequence`` detects string concatenation inside lists, sets & tuples.
Example of code that would generate such warning: