pylint_runner
A simple pylint application that scans the current directory and any sub-directories recursively, then runs pylint on all discovered .py files.
Dependencies
Installation
Preferred installation method:
pip install pylint_runner
From source:
python setup.py install
When installed, this will create an executable pylint_runner, pylint_runner#, and pylint_runner#.# where the first # represents the major version of Python (2 or 3) and the second # represents the minor version of Python. So if installed by Python 2.7, you will have available pylint_runner, pylint_runner2, and pylint_runner2.7 so as to allow usage by however many installed versions of python on the system as pylint is version dependent on its output (due to using the Python AST).
Usage
pylint_runner
Output is standard pylint output. There should be no output if no issues were found.
In case of issues, you should see output similar to:
************* Module foo.bar C: 24, 0: Missing function docstring (missing-docstring) ************* Module tests.foo_tester C: 19, 0: Final newline missing (missing-final-newline) C: 19, 0: Invalid constant name "a" (invalid-name)
Additional Arguments
See the standard help ouput:
pylint_runner -h
NOTE: Unused options and arguments will be passed directly to pylint. For example, doing pylint_runner -d C0103 -d E0602 will cause pylint -d C0103 -d E0602 on each file.
Verbose mode
pylint_runner -v
Verbose mode lists all files that were found for testing immediately, along with the pylint output.
This will generate (if run against this repo):
Using pylint 1.6.5 for python 2.7.11 pylint running on the following files: - pylint_runner/__init__.py - pylint_runner/main.py - setup.py - tests/__init__.py - tests/test_runner.py - tests/tests/dummy.py ************* Module tests.test_runner I: 1, 0: Locally disabling missing-docstring (C0111) (locally-disabled)
rcfile
This allows you to specify a pylintrc file to be used using –rcfile path_to_file.
It may be a relative, or absolute path and defaults to .pylintrc at the current working directory.
It will read the value of ignore from the rcfile and ignore any matching files/folders while building the list of files to pass to python.
It will also pass that rcfile for use by pylint.
Metadata
Release files for pylint-runner 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pylint_runner-0.7.0.tar.gz | 6.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pylint_runner-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.4 kB
Release files / pylint_runner-0.7.0.tar.gz
| Download URL | pylint_runner-0.7.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
939459a20eea44550631ec27cb64912970c6c14693dfccd43120c636cf8273b5
|
|
BLAKE2b-256 checksum How to use checksums |
e5feb7aefd8a8dac3703a44565a2575b0df9ae9ecad2283cb38c0554d3640b09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.10.12
|
Release files / pylint_runner-0.7.0-py3-none-any.whl
| Download URL | pylint_runner-0.7.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ae147800ac6a3f279fb046e6ec02f6ac9866854628a8145d2199c39f80865c0
|
|
BLAKE2b-256 checksum How to use checksums |
45ea2a24a8a4575385104f55cfd4ab2bb6b71294d8b9197870796a683aca9577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.10.12
|
Security for pylint-runner 0.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.