Flake8 VS mypy

The wemake.services team describe wemake-python-styleguide as *the strictest and most opinionated Python linter ever*. It's essentially the flake8 package, a linting tool that analyses code for defects, with plugins. Its primary objectives are:

When working with several people on one project, it is very often necessary to use a single style of code design, writing comments, using variable names, etc. In the Python world, we use linters flake8, various formatters (black, yapf, autopep8) and mypy for type checking. How can Dart help meet these challenges?

Python has a bunch of tools like black, pylint, flake8.

Yay! Maybe now flake8 will finally support project.toml.

flake8: Flake8 is a wrapper around these tools: PyFlakes pycodestyle Ned Batchelder's McCabe script

yaml repos: - repo: https://github.com/myint/autoflake rev: v1.4 hooks: - id: autoflake args: - --in-place - --remove-all-unused-imports - --expand-star-imports - --remove-duplicate-keys - --remove-unused-variables - repo: https://github.com/asottile/pyupgrade rev: v2.29.0 hooks: - id: pyupgrade args: [--py36-plus] - repo: https://github.com/PyCQA/isort rev: 5.9.3 hooks: - id: isort - repo: https://github.com/psf/black rev: 21.10b0 hooks: - id: black args: [--safe, --quiet] - repo: https://github.com/PyCQA/flake8 rev: 4.0.1 hooks: - id: flake8 - repo: local hooks: - id: pylint name: pylint entry: pylint language: system types: [python] args: [ "-rn", "-sn", ] - repo: https://github.com/pre-commit/mirrors-mypy rev: v0.910-1 hooks: - id: mypy name: mypy entry: mypy language: python types: [python] args: [] require_serial: true - repo: https://github.com/pre-commit/mirrors-prettier rev: v2.4.1 hooks: - id: prettier args: [--prose-wrap=always, --print-width=88]

A code linter should help developers identify potential errors and coding style violations in your code; and I think Flake8 can accomplish that. Flake8 combines PyFlakes, pycodestyle, and Ned Batchelder's McCabe script to enhance our Python code quality.

how, when mypy itself has only "type: ignore" as a workaround for many scenarios?

here's a list of 41 issues where either the user or the mypy devs are saying "use type: ignore as a workaround for now":

https://github.com/python/mypy/issues?q=is%3Aopen+label%3Afa...

It reminds me of this 5 year old bug in mypy: "int is not a Number?" [1].

[1]: https://github.com/python/mypy/issues/3186

Mypy is an optional static type checker that aims to combine the benefits of dynamic (or “duck”) typing and static typing. The benefits of statically typed code are increased readability and maintainability. For an existing code base here's a guide on how to implement Mypy.

mypy – Optional static typing for Python

You might get some luck by asking it on the mypy repo.

Been looking into it a bit more. I think you're right, it's not supported. Turns out mypy only has very limited support for type hinting metaclasses. This page suggests it may be possible to support this with a mypy plugin, but I'm really not looking to do something that involved. Just wanting to hint an existing API :/ I suppose I could look into tweaking the API to be more hint-able, but I think I'll just accept this piece isn't perfect.

When working with several people on one project, it is very often necessary to use a single style of code design, writing comments, using variable names, etc. In the Python world, we use linters flake8, various formatters (black, yapf, autopep8) and mypy for type checking. How can Dart help meet these challenges?

Since Python 3.5, type annotations can be used for possible static analysis, refactoring, runtime type checking and code generation. An optional static type checker named mypy supports compile-time type checking.

Also, there’s Mypyc.