Does the following snippet from typeshed correctly and completely type classmethod, and if so, does a static type checker need to special case (hard code) classmethod instead of treating it correctly like a decorator?

[kwsp]

https://github.com/python/typeshed/blob/f28cb8b8562ccc382d018129ba4886f241c6db9c/stdlib/builtins.pyi#L146-L160

class classmethod(Generic[_T, _P, _R_co]):
    @property
    def __func__(self) -> Callable[Concatenate[type[_T], _P], _R_co]: ...
    @property
    def __isabstractmethod__(self) -> bool: ...
    def __init__(self, __f: Callable[Concatenate[type[_T], _P], _R_co]) -> None: ...
    @overload
    def __get__(self, __instance: _T, __owner: type[_T] | None = None) -> Callable[_P, _R_co]: ...
    @overload
    def __get__(self, __instance: None, __owner: type[_T]) -> Callable[_P, _R_co]: ...
    if sys.version_info >= (3, 10):
        __name__: str
        __qualname__: str
        @property
        def __wrapped__(self) -> Callable[Concatenate[type[_T], _P], _R_co]: ...

Pyright special cases (hard codes) classmethod, and I'm pretty sure other type checkers do too. By doing so, they avoid having to parse the above type annotations and work with descriptors correctly.

[erictraut]

I think your question is based on faulty assumptions. Refer to this explanation for details.

[kwsp]

@erictraut Thanks for taking the time to explain! I will need some time to digest this information.

[kwsp]

@erictraut I made a proposal for typing.no_discard. Would love to get your input!