mypy VS black

It looks like there's a PEP for that already! [0]

And as (almost) always, Pyright has already implemented the provisional PEP!

[0] https://github.com/python/mypy/issues/4441

They don't work in the way you would think for dataclasses or at all for dicts/TypedDicts.

See this for dataclasses: https://github.com/python/mypy/issues/5374#issuecomment-8841....

It's worth noting that Python 3.5+ added standardized type annotations for 3rd party type checkers to leverage. I pretty much use them all the time now except for extremely small scripts. My 3rd party type checker of choice is mypy.

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.

The interactivity of notebooks makes it simple to try out new ideas, but it also yields messy code. While exploring data, we often rush to write code without considering readability. Lucky for us, there are tools like isort and black which allow us to easily re-format our code to improve readability. Unfortunately, these tools only work with .py files; however, soorgeon enable us to run them on notebook files (.ipynb):

Your code isn't PEP-8 compliant. Use black or autopep8 on your code to auto-format your code, or at least use pylint to check for issues, before asking anyone else to read your code.

Not so much for the project but for project support I always use black for formatting. mypy to check my code. pydocstyle to check the comments.

Use black code formatter.

black for the win

To somewhat misquote Pirates of the Caribbean- code formatting is more what you'd call "guidelines" than actual rules. In my opinion, do what's comfortable for you or the team you're working with. These days I tend to just use black (which will adhere to the one statement per line mantra): https://github.com/psf/black

I have some feedback for you on the code itself. Typically, you should follow PEP8 naming conventions, your function names should have all lower case. Your classes should be camel case (CamelCase). Getting used to a good naming convention is vital and will make things easier for you in the long run. I also use a code format tool called black. It helps to make things very consistent. It isn't mandatory, just an FYI.

Run black on save https://github.com/psf/black Most modern IDE's allow this. Just google "name of your editor + black on save".