Don't require annotations of kwargs initialized to bool, float, int or string constants

See PR: #12918 (draft).

Feature

There should be no need for annotations for kwargs in the following (partial) function definitions:

def bool_args(ok=True, die=False)
def int_arg(i=1)
def float_arg(ratio=1.0)
def string_arg(s="Hello World")

In this example, the natural annotations are as follows:

def bool_args(ok: bool=True, die: bool=False): pass
def int_arg(i:int=1): pass
def float_arg(ratio: float=1.0): pass
def string_arg(s:str="Hello World"): pass

The issue proposes a non-trivial change to mypy's type inference. The proposal suggests that mypy act as if a natural annotation exists for an initialized kwarg. Note: mypy will (must!) check the new (natural) annotation, and mypy must complain if the natural annotation is not correct.

Pitch

At present, with disallow_untyped_defs = True and disallow_incomplete_defs = False, mypy complains that the signatures above lack annotations for the kinds of kwargs shown above. Such annotations unnecessarily clutter code. It should be possible to infer the types of the kwargs based on the obvious types of the constants!

This feature would fix my biggest gripe about mypy :-)

Commencez par examiner la PR préliminaire #12918 et les exemples de l'issue d'annotations naturelles pour les arguments nommés initialisés avec des constantes bool, int, float et string. Suivez le comportement pertinent de l'inférence de types et vérifiez que les annotations inférées sont contrôlées pour garantir leur exactitude. Le travail est terminé lorsque ces cas satisfont disallow_untyped_defs sans annotations explicites, tandis que les valeurs par défaut invalides continuent de produire des erreurs.