Opened 7 years ago
Last modified 3 years ago
#29299 new Cleanup/optimization
Inline/Out of the box Type hints(PEP 484) and Variable annotations(PEP 526) — at Initial Version
| Reported by: | Andreas Galazis | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | 2.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Adam Johnson, Zach Borboa, Vlastimil Zíma | Triage Stage: | Someday/Maybe |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Adhering to Type hints(PEP 484) / type annotations could contribute to being more explicit / performing code analysis and checks on Django projects. Intellisense based on type annotations can also contribute to faster and less error-prone coding experience.
Typesheds will be a pain to maintain across versions. Based on my experience with typescript typings, the most immaculate situation is shipping typings within the project, even though shipping external typings is mature in that case. Nevertheless, inline typings can help Django project development as well.
Adding to the docs any future plans regarding this, would be helpful for prospective developers.
Note:
See TracTickets
for help on using tickets.