codacy/codacy-pylint

Pylint tool for Codacy

Codacy Pylint

This is the docker engine we use at Codacy to have Pylint support. You can also create a docker to integrate the tool and language of your choice! See the codacy-engine-scala-seed repository for more information.

Usage

You can create the docker by doing:

docker build -t codacy-pylint:latest .

The docker is ran with the following command:

docker run -it -v $srcDir:/src codacy-pylint:latest

Generate Docs

1. Update the version in docs/patterns.json

2. Run the DocGenerator:

   sbt "doc-generator/run"

Test

We use the codacy-plugins-test to test our external tools integration. You can follow the instructions there to make sure your tool is working as expected.

What is Codacy?

Codacy is an Automated Code Review Tool that monitors your technical debt, helps you improve your code quality, teaches best practices to your developers, and helps you save time in Code Reviews.

Among Codacy’s features:

• Identify new Static Analysis issues
• Commit and Pull Request Analysis with GitHub, BitBucket/Stash, GitLab (and also direct git repositories)
• Auto-comments on Commits and Pull Requests
• Integrations with Slack, HipChat, Jira, YouTrack
• Track issues in Code Style, Security, Error Proneness, Performance, Unused Code and other categories

Codacy also helps keep track of Code Coverage, Code Duplication, and Code Complexity.

Codacy supports PHP, Python, Ruby, Java, JavaScript, and Scala, among others.

Free for Open Source

Codacy is free for Open Source projects.

codacy-pylint's Issues

Pattern E0401 gives false positives

The pattern E0401 searches for missing imports. This is something a Codacy tool can't do because it doesn't download dependencies.
This pattern should be blacklisted.

Add support for Python 3.6+

Python 3.6 (released 2 years ago) introduced new syntax for string formatting (f-strings), see https://www.python.org/dev/peps/pep-0498/ for details.

codacity-pylint uses Python 3.5 and reports f-strings as syntax errors.

Any plans on supporting 3.7 and 3.8?

codacy-pylint/src/codacy_pylint.py

Line 81 in 0e4721f

["python3.6", "-m", "pylint"] + # Pylint 1.9.5 doesn't support Python 3.7

[CY-6634] "Django was not configured" error even when not specified in custom configuration

When using a custom pylint configuration file, even though pylint_django is not specified in load-plugins, codacy will report an issue:

Django was not configured. For more information run pylint --load-plugins=pylint_django --help-msg=django-not-configured (django-not-configured (E5110))

It seems the plugin is always loaded here and ignores custom configuration.

Codacy/pylint import issue

I have a structure:

myproject/
    app_main.py
    my_app_files/
        some_script.py

app_main calls a some_functon from some_script via from my_app_files.some_script #import some_function - which seems to be how PEP8 suggests.
Yet Codacy seems to want met to reform it to from _master.my_app_files.some_script import some_function - which not only doesn't work, it doesn't make a lot of sense, since _master doesn't appear anywhere in my project.

toonarmycaptain/dionysus#5

Question. f-string Syntax Error

I have some problems about codacy syntax check.

But I found some issue and pr #38

But this problem have been occured until now. I want to know the reason this occured

Pylint picks wrong module in case of naming collision

False positive with pattern E0611 with message No 'thing' in module 'module' is thrown.
Codacy is pulling the wrong module when there are 2 modules with the same name in different directories.