HackSoftware/Django-Styleguide
1
1
Fork 0
mirror of https://github.com/HackSoftware/Django-Styleguide.git synced 2024-11-22 01:26:43 +03:00
Code Issues Packages Projects Releases Wiki Activity

Add clarity to the mypy section

Browse Source 
- Drop tweet link
- Resolve #126
This commit is contained in:
Radoslav Georgiev 2023-05-01 17:43:15 +03:00
parent 969a8e953e
commit 8487eac3c9
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -2741,10 +2741,14 @@ A section with various things that can make your Django developer life better.
### `mypy` / type annotations
When it comes to using type annotations, alongside [`mypy`](https://mypy.readthedocs.io/en/stable/index.html), [this tweet](https://twitter.com/queroumavodka/status/1294789817071542272) **resonates a lot with our philosophy.**
When it comes to [`mypy`](https://mypy.readthedocs.io/en/stable/index.html), we have the following philosophy:
- We have projects where we enforce `mypy` and are very strict about it.
- We have projects where types are looser and `mypy` is not used at all.
> Use it, if it makes sense for you & helps you produce better software.
In HackSoft, we have:
- Projects where we enforce `mypy` and are very strict about it.
- Projects where types are more loose and `mypy` is not used at all.
Context is king here.