dejalint
dejalint is yet another linter.
Installation
Install via pip:
pip install dejalintConfiguration
Every command-line option can also be set in pyproject.toml. The file is looked up from the current directory upwards, and command-line arguments take precedence over it. Paths are relative to the pyproject.toml location.
[tool.dejalint]
paths = ["src", "tests"]
min-nodes = 8
format = "line" # or "rule"Suppressing violations
Add a noqa comment with the rule code either on the def / class line or right at the top of its body. A suppressed definition is left out of the comparison entirely, so marking either copy silences the pair.
def squares(xs): # noqa: DJL001
...
def squares(xs):
# noqa: DJL001
...A bare # noqa without codes does not affect dejalint. If you use Ruff, declare the codes as external so it doesn’t report them as unknown:
[tool.ruff.lint]
external = ["DJL"]Pre-commit
repos:
- repo: https://github.com/kqf/dejalint
rev: v0.x.y
hooks:
- id: dejalint1 maintainer
Metadata
1 maintainer
Release files for dejalint 0.0.4
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 | |
|---|---|---|---|---|
| dejalint-0.0.4.tar.gz | 7.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dejalint-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.0 kB
Release files / dejalint-0.0.4.tar.gz
| Download URL | dejalint-0.0.4.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7bedbee28a2375614234f3d69cf0531e29772bddfad12c58e6a83b8591fc471
|
|
BLAKE2b-256 checksum How to use checksums |
7d5661ec2d4af83c726ff3d7ef47345d86dfdfcf35f5fca29d411ad7f05e3e95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / dejalint-0.0.4-py3-none-any.whl
| Download URL | dejalint-0.0.4-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7664546e242143428b1a98a0b483673e9d45f62b2e5631ae0027ccc547b2b83a
|
|
BLAKE2b-256 checksum How to use checksums |
0ec61d29bbba46e680410a8a532c79dd15bb056cd2339ecf1f34428c962222b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for dejalint 0.0.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dejalint-0.0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA 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.
