Sorry for the late answer, I didn't have time to read this mailing list for the
last month :-( Here's my position on the matter.
Adding type annotations only makes sense if a type checker checks them.
Otherwise, they're unlikely to be correct and usable, so it would be
counterproductive to add
Thanks for sharing your answer publicly Adam and Markus. Here are the
points I brought up in the discussion
>From my limited experience with type annotation on a large monolithic code
> base that was ported from Python 2 to 3 even gradual typing has been a lot
> of trouble for the few benefits
Thanks for pushing this public, Adam. In the discussion I brought up these
points.
I've been using static typing in Python for about 1.5 years now. Every now and
then it's neat, but often enough I get annoyed by it. Either because I simply
don't know how to use the tools at hand correctly or be
So we in the technical board were a bit opaque and had our discussion in
private before Carlton posted our summary. Apologies for this. We'll repeat
the discussion in the open so you can see our reasoning.
On 4 March Carlton prompted for our input. I replied:
My experience using types, so far:
>
Hi all.
The question of using typing, or type hints, or type checking, in (or with)
Django
has come up several times. Whether we would add inline annotations, or use
stub
files, or what?
Most recently, this resulted in a draft DEP[0] to try and formalize the
situation,
followed by a PR[1] ad
