flake8-type-ignore
flake8-type-ignore allows you to disallow type: ignore comments in your
typed Python code.
Usage
When installed into your Python environment running flake8, this plugin will
raise errors according to the table below. For example, installing this plugin
will raise flake8 errors in the following code:
# This line raises TI100
x: str = 1 # type: ignore
# This line raises both TI101 and TI139
x.y = 2 # type:ignore[attr-defined,misc]
def print_only_strings(arg: str):
print(arg)
# This line raises TI104
print_only_strings(123)
Error codes
| flake8-type-ignore error code | mypy error code |
|---|---|
TI001 |
Meta error code for invalid type: ignore comments. |
TI002 |
Meta error code for unknown mypy error codes. |
TI100 |
Bare type: ignore comment |
TI101 |
attr-defined |
TI102 |
name-defined |
TI103 |
call-arg |
TI104 |
arg-type |
TI105 |
call-overload |
TI106 |
valid-type |
TI107 |
var-annotated |
TI108 |
override |
TI109 |
return |
TI110 |
return-value |
TI111 |
assignment |
TI112 |
type-arg |
TI113 |
type-var |
TI114 |
union-attr |
TI115 |
index |
TI116 |
operator |
TI117 |
list-item |
TI118 |
dict-item |
TI119 |
typeddict-item |
TI120 |
has-type |
TI121 |
import |
TI122 |
no-redef |
TI123 |
func-returns-value |
TI124 |
abstract |
TI125 |
valid-newtype |
TI126 |
str-format |
TI127 |
str-bytes-safe |
TI128 |
exit-return |
TI129 |
no-untyped-def |
TI130 |
no-untyped-call |
TI131 |
redundant-cast |
TI132 |
comparison-overlap |
TI133 |
no-any-unimported |
TI134 |
no-any-return |
TI135 |
unreachable |
TI136 |
redundant-expr |
TI137 |
name-match |
TI138 |
syntax |
TI139 |
misc |
License
flake8-type-ignore is available under the BSD 3-Clause license. See the LICENSE file for more details.
Metadata
Release files for flake8-type-ignore 0.1.0.post2
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 |
|---|---|---|---|---|
| flake8-type-ignore-0.1.0.post2.tar.gz | 5.3 kB | Without provenance | Details for flake8-type-ignore-0.1.0.post2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flake8_type_ignore-0.1.0.post2-py3-none-any.whl | Python 3 | none | any | Details for flake8_type_ignore-0.1.0.post2-py3-none-any.whl |
Total release size: 11.1 kB
Release files / flake8-type-ignore-0.1.0.post2.tar.gz
| Download URL | flake8-type-ignore-0.1.0.post2.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e9cc986053cdd24570000c92254f1d73b33446b89a471f0d1a31e77f59a6115
|
|
BLAKE2b-256 checksum How to use checksums |
0ff41d35202e735075d0c321541a753a0dd24fed166ee4b63c486a47af7e9a6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Release files / flake8_type_ignore-0.1.0.post2-py3-none-any.whl
| Download URL | flake8_type_ignore-0.1.0.post2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dae67f10ad5193c80d9656475f01a9dea5819241103a7254583aaddbeffc3fef
|
|
BLAKE2b-256 checksum How to use checksums |
9374c49146d2e9c8092cf7b1f926105c9da774a90d78c0efba7be6e1114e9077
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Security for flake8-type-ignore 0.1.0.post2
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.