| 201 | | === Strict-mode support for django-stubs === |
| 202 | | |
| 203 | | The django-stubs implementation does not currently pass Mypy’s strict mode. |
| 204 | | |
| 205 | | Making this compliant would enable users to always use strict mode with them, improving type safety. Expected outcome would be a PR doing that. |
| 206 | | |
| 207 | | === Merging django-types back into django-stubs === |
| 208 | | |
| 209 | | There is a spin-off project from django-stubs called django-types. The original intention here was for it to be merged back into django-stubs, but that's never happened. |
| 210 | | |
| 211 | | django-types removes the need to use any mypy plugins, making it possible to use type checkers other than mypy, such as Pyrite, Pyre, etc. |
| 212 | | |
| 213 | | django-types is not actively maintained, however, and having competing stubs implementations means neither is as strong as could be. |
| 214 | | |
| 215 | | There is a small project in extracting the work from django-types and creating a PR for django-stubs allowing it to be merged back in, and effort to be concentrated on the single implementation. |
| | 199 | === Expand coverage === |
| | 200 | |
| | 201 | django-stubs uses Mypy’s stubtest tool to check that its type hints align with Django’s source, per [https://github.com/typeddjango/django-stubs/blob/master/CONTRIBUTING.md#testing-stubs-with-stubtest the contributing documentation]. The “todo” file contains ~1600 functions and classes missing type hints. A proposal targeting a specific, significant subset of the missing types is likely to be accepted. |