| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add ``consider-using-f-string`` checker
This adds a checker for normal strings which are formatted
with ``.format()`` or '%'.
The message is a convention to nudge users towards using f-strings.
This closes #3592
* Update pylint code to use f-strings
After adding `consider-using-f-strings` the codebase showed numerous
cases of formatting which could be f-strings.
This commit changes most of these to become f-strings, or adds ignores.
* Apply suggestions from code review
Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
* Fix link in license header
* Update link to astroid bump_changelog
|
| | |
|
| |
|
|
|
|
|
|
| |
* Implement consider-using-with check
* Fix or disable consider-using-with in codebase
* Fix ticket number in ChangeLog
* Move functional test for ``open()`` into separate testfile and exclude this test from running with PyPy
Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
using configuration:
```yaml
- repo: https://github.com/asottile/pyupgrade
rev: v2.1.0
hooks:
- id: pyupgrade
args: [--py3-plus, --keep-percent-format]
exclude: ^tests/(extensions/data/|functional/|input/|regrtest_data/)
```
|
| |
|
|
| |
We no longer support Python 2 so we can remove
the compatibility code we had in place for that version.
|
| |
|
|
|
|
| |
not a Python one.
Close #2837
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Fixes a bug where epylint ignores settings in pylintrc
due to hard coded default arguments. Now with this fix,
the output of epylint is identical to pylint.
|
| |
|
|
|
|
|
|
|
|
| |
* Fix shlex parsing error on Windows in epylint
Closes #1940
* Change py_run's shlex posix sys.platform
sys.platform mistakenly included darwin as not posix compliant
|
| |
|
|
|
| |
This example has been introduced in #5821.
However, it does not work any more.
Closes #1870
|
| | |
|
| |
|
|
|
| |
methods. (#1641)
Close #1267
|
| |
|
|
|
|
|
| |
The way this object is defined, won't let the user modify the message
template when pylint is called from a python script. Rearranging the
order of variables on its definition prevents this behavior.
Signed-off-by: Daniela Plascencia <daniela.plascencia@linux.intel.com>
|
| | |
|
| |
|
|
|
| |
This was changed automatically in #894, but apparently
we need to have the copyright notice somewhere.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
epylint.py_run was calling *epylint* script in order to
do the computation. But this was prone to failures,
in the case where we have multiple installations of Pylint,
for different Python versions, which actually led to crashes
when a Python 2's py_run call was calling epylint's belonging
to Python 3. Instead of calling epylint script directly,
we are calling Python with our known epylint code.
In order to do this, we also had to switch the shell argument
to False.
Closes #441
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This gets rid of a potential issue which can occur if epylint was calling pylint
with lint.py instead. When this was happening, the first entry of sys.path would
have been the directory of pylint which contains lint.py. At the same time, if
someone analyzes, with epylint, a file that contains an import of a module,
and that module has the same name as one of the modules that are coming along
with pylint's lint.py, then instead of importing the module from site-packages,
the pylint's module would have been imported instead.
Close #920
|
| | |
|
| |
|
|
|
|
| |
.wait()
Close #599
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
C0102,C0112,C0121,C0202,C0203,C0204,C0301
|
| |
|
