Consulting services: if your organisation needs a reputable software developer with a track record of producing high-quality and maintainable Python/Django code, please get in touch to discuss your needs. More info
Ideas
Default manager with restrictive get_query_set()
Oldforms (?)
- Overring definition of model. Eg:
- class MyModel(models.Model):
foo = [..] foo = [..]
Not importing settings via “django.conf import settings”
Not using reverse (or @permalink) in get_absolute_url (?)
Form definitions in models.py
Ignore tests
Models
Don’t count ManyToMany fields on a model as a field
Remove common prefix checking.
models.. specifying “objects = “ should be last
Views
Calling request.is_authenticated without actually calling function
order_by(‘?’)
request.method.upper is a no-op (etc.)
cache.set without a timeout
URLS
Unreversible urlpatterns
Layout
Form class not in forms.py
Admin class not in admin.py
Templates
{% if foo %}{{ foo }}{% else %}bar{% endif %} => {{ foo|default:”bar” }}
{% with foo as bar %} … [ not using {{ bar }} ] … {% endwith %}
{% endblock %} vs. {% endblock blockname %}
Settings
Ordering of MIDDLEWARE_CLASSES
TEMPLATE_DIRS not absolute
Layout
forms not in forms.py managers not in managers.py
Metadata
Release files for django-lint 2.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 | |
|---|---|---|---|---|
| django-lint-2.0.4.tar.gz | 8.1 kB | Without provenance | Details |
Release files / django-lint-2.0.4.tar.gz
| Download URL | django-lint-2.0.4.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25f28091d40f4586aa46cd3cab3d98665067ade95d7a45013ab24f03bb9989f1
|
|
BLAKE2b-256 checksum How to use checksums |
43c394dcb0344e65ecf383deab434733f057dd3479cf7387638c6cc5813ecaca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-lint 2.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.
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.