To me one approach would be to put a cut off for any merged code /PR start
inlining type hints/annotations for all new code. This seems to simple to
be a solution but at the end of the day as code gets updated even
bigger part of the codebase will have type hints. The question is whether
parti
I agree with you, but at some point, we could combine solid annotated core
with a cut off for non annotated code? Otherwise, this will end up being a
loop.
On Wednesday, 11 April 2018 17:16:21 UTC+3, dmoisset wrote:
>
>
>
> On 11 April 2018 at 11:21, Andreas Galazis > wrote:
Just stumbled on this blog post:
https://www.willmcgugan.com/blog/tech/post/adding-type-hints-to-the-django-orm/.
An interesting but too theoretical suggestion: We could even get rid of
field/ field configuration. But I guess that's far ahead of what we are
trying to achieve xD.
On Wednesday,
