This Pylint plugin minimizes Pylint’s complaints about web2py code. Web2py executes user code in special environment populated with predefined objects and types and with objects defined in model files. Also it has magic import mechanism which knows some special places where to find modules.
Pylint doesn’t know about these details – its parser is unable to find these objects and modules, resulting in a flood of laments. This plugin: - adds variables defined in models to other models’ and controllers’ scope - adds definition of some predefined global objects to models and controllers - adds web2py module paths to sys.path, so pylint is able to find them
To enable this plugin: - Add –load-plugins=pylint_web2py2 to pylint options or - Add load-plugins=pylint_web2py2 to your .pylintrc
Metadata
Release files for pylint_web2py2 0.8
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 | Actions |
|---|---|---|---|---|
| pylint_web2py2-0.8.tar.gz | 3.6 kB | Without provenance | Details for pylint_web2py2-0.8.tar.gz |
Release files / pylint_web2py2-0.8.tar.gz
| Download URL | pylint_web2py2-0.8.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd29a3ffbb48071bf69e00912784013216046a15d1641fa0613ba1546709b6d2
|
|
BLAKE2b-256 checksum How to use checksums |
565413cbb62d62ccf1caf74cb54fd2a8ec8bb3507669f9c2b1b66ae729d7ec05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pylint_web2py2 0.8
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.