Return types for Overloads with "Optional[TypeVar]" arguments are deducted as just "object"
Personne n'a encore pris cette issue.
- Langage dominant
- Python
- Étoiles
- 20.6k
- Forks
- 3.3k
- Métriques de merge des PR
- Métriques de PR en attente
Description
Bug Report
Please see the following mypy playground: https://mypy-play.net/?mypy=latest&python=3.12&gist=207fe333eb8e226d36b84bf34be5ca65
I personally encountered this on mypy 1.7.1 and Python 3.8, but the mypy playground link uses the latest version of everything.
Consider the following helper function:
import datetime
from typing import Any, Optional, Sized, Tuple, Type, TypeVar, Union
from typing_extensions import Literal, overload, TypeAlias
_T = TypeVar("_T")
class TypeGuardError(Exception):
pass
_THasLen = TypeVar("_THasLen", bound=Sized)
@overload
def required(
value: Optional[_T],
*,
message: Optional[str] = None,
property_name: Optional[str] = None,
) -> _T:
pass
@overload
def required(
value: Any,
*,
instance_of: Type[_T],
instance_of_message: Optional[str] = None,
message: Optional[str] = None,
property_name: Optional[str] = None,
) -> _T:
pass
def required(
value: Optional[Any],
*,
instance_of: Optional[Any] = None,
message: Optional[str] = None,
property_name: Optional[str] = None,
instance_of_message: Optional[str] = None,
) -> Any:
if property_name is not None:
message_prefix = f"{property_name}: "
else:
message_prefix = ""
if value is None:
raise TypeGuardError(message or f"{message_prefix}Value cannot be `None`.")
if instance_of and not isinstance(value, instance_of):
raise TypeGuardError(
instance_of_message
or message
or f'{message_prefix}Expected value of type "{instance_of.__name__}", got value of type "{type(value).__name__}" instead.'
)
return value
required here just checks if the value is not None, optionally verifying its type as well. If any validation fails, it's able to generate an error, with either a message you define, or a parameterizable auto-generated one.
The returned value is just the input value, but cast to its "pure type" through overloading (removing None from the type by type-matching it to Optional). But when passing the instance_of argument, the return type is whatever type you pass to that argument instead. That's the intention.
However, mypy fails my expectations. For example:
TimeDeltaLike: TypeAlias = Union[int, float, str, datetime.timedelta]
default_lock_time: Optional[TimeDeltaLike] = None
locked_for = required(
default_lock_time,
message=f"Entity does not specify a default lock time.",
)
# QUESTION: Why is the revealed type `object`?
reveal_type(locked_for)
In the last line, the revealed type is object.
When analyzing the same code through Pyright, the revealed type is int | float | str | datetime.timedelta, as I would expect.
To Reproduce
# Ideally, a small sample program that demonstrates the problem.
# Or even better, a reproducible playground link https://mypy-play.net/ (use the "Gist" button)
See explanation above.
Expected Behavior
See explanation above.
Actual Behavior
See explanation above.
Your Environment
- Mypy version used: 1.7.1
- Mypy command-line flags:
- Mypy configuration options from
mypy.ini(and other config files): - Python version used: 3.8
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par le mypy playground lié et les surcharges required utilisant Optional[TypeVar] ; examinez comment l’appel avec default_lock_time est inféré avant reveal_type. Le travail est terminé lorsque le type de retour révélé est int | float | str | datetime.timedelta plutôt que object, tout en préservant le comportement des surcharges instance_of.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- devtools
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 42/100