|
3 | 3 | *************************** |
4 | 4 |
|
5 | 5 | :Release: 2.11 |
6 | | -:Date: TBA |
| 6 | +:Date: 2021-09-16 |
7 | 7 |
|
8 | 8 | Summary -- Release highlights |
9 | 9 | ============================= |
10 | 10 |
|
| 11 | +In 2.11, we added a new default checker to advise using f-string as it's |
| 12 | +the most efficient way of formatting strings right now. You can use |
| 13 | +`pyupgrade`_ to migrate your old ``%`` and ``format()`` automatically. |
| 14 | + |
| 15 | +We added a new extension ``SetMembershipChecker`` that will advise the |
| 16 | +use of set for membership test, as it's more performant than lists or tuples. |
| 17 | +The ``CodeStyleChecker`` also got some love, check it out if you're not already |
| 18 | +using it. |
| 19 | + |
| 20 | +We fixed some long standing bugs, false positives, or false negatives and |
| 21 | +we added small quality of life options like ``min-similarity-lines`` that |
| 22 | +disable the duplication check when set to 0. |
| 23 | + |
| 24 | +Under the hood the code for both pylint and astroid is progressively more typed, |
| 25 | +which could be helpful to you if you're using them as libraries. In order for |
| 26 | +this new typing to make more sense and stay simple, we deprecated some functions |
| 27 | +or type that will be removed in the next major version. This is an ongoing effort. |
| 28 | + |
| 29 | +The future ``possible-forgotten-f-prefix`` check still had too much false positives, |
| 30 | +and is delayed again. Check the `possible-forgotten-f-prefix`_ issue if you want |
| 31 | +to provide knowledge or use case :) |
| 32 | + |
| 33 | +.. _possible-forgotten-f-prefix: https://github.com/PyCQA/pylint/pull/4787 |
| 34 | +.. _pyupgrade: https://github.com/asottile/pyupgrade |
| 35 | + |
11 | 36 |
|
12 | 37 | New checkers |
13 | 38 | ============ |
|
0 commit comments