Cannot assign to field of Callable type

Consider this example:

from typing import Callable

class A:
    f = None  # type: Callable[[int], int]

    def __init__(self, g: Callable[[int], int]) -> None:
        self.f = g

mypy reports:

trial.py: In member "__init__" of class "A":
trial.py, line 7: Cannot assign to a method
trial.py, line 7: Invalid method type
trial.py, line 7: Incompatible types in assignment (expression has type Callable[[int], int], variable has type Callable[[], int])

while I'd expect this to work.

Note that there is a second error in the reporting of the type of the variable.

Also, this passes type checking (correctly):

f = None  # type: Callable[[int], int]

def g(x: int) -> int: return 0

f = g

The mismatching types is probably because mypy thinks f is a method and therefore strips off the first argument (self).

Hmm.. actually not sure what's the right thing to do here. Based on a quick experiment, the desired behavior seems to depend on what kind of a callable g is in your original example.

Consider this:

class A:
    f = None
def m(x):
    return x + 1
print(m(1))  # 2
A.f = m
print(A().f(1))  # Error (2 args given, expects 1)

But now look at this:

class A:
    f = None
class M:
    def __call__(self, x):
        return x + 1
m = M()
print(m(1) # 2
A.f = m
print(A().f(1))  # Okay => 2

Taking off priority label because the fix doesn't seem obvious.

Before reporting it I also thought for a while that I could fix it quickly 😄.

Is there any update? The issue is still present. For some real world example, it is used in the ctypes module (in the examples).

from typing import Any, Callable

class A():
    a = lambda: None  # type: Callable[..., None]

def f() -> None: return None

A().a = f

gives

/tmp/assign_callable.py:8: error: Cannot assign to a method
/tmp/assign_callable.py:8: error: Incompatible types in assignment (expression has type Callable[[], None], variable has type Callable[..., None])

Having Callable[..., None] or Callable[[], None] do not resolve it, having Callable[..., Any] remove the incompatible types line.

I'm sorry, I don't have any further updates.

Thanks for bumping this with the new repro!

It's possible these two errors are different issues. The second looks like it may be a case of the Void/NoneTyp distinction (recently eliminated in our --strict-optional future: #1975). Would you try reproducing it on master and with --strict-optional?

The first error looks like the same thing as the original issue.

@tharvik

@tharvik, would you also link more specifically to the bit in ctypes that refers to this? It's good to know about that use case, and it'd be interesting to see it more concretely.

@gnprice

Seems that I'm unable to reproduce 'Incompatible types in assignment' on master with or without --strict-optional.

@gnprice in ctypes, when declaring a foreign function, one can redefine errcheck, which should be a callable. It allows processing of the return value (and raising on failure).

Example from the documentation

def errcheck(result, func, args):
    if not result:
        raise WinError()
     return args

GetWindowRect.errcheck = errcheck

This way, we can load a library, in which, every attribute is a foreign function, then assign to some an errcheck for freeing some pointer or other.

For another example, here goes libLAS, where the library is loaded then it is assigned some checks.

To be clear, the example still produces "Cannot assign to a method". The problem seems to be that mypy disallows assigning to a method (which I think is reasonable) but thinks that a class variable declared with a Callable type (and initialized with a lambda) is also a method. The latter is wrong, I think.

Fix callable instance variable support (python#10548)

Fix callable instance variable support (take 2) (#13400)

type hint application wrapper monkeypatch

Ignore mypy errors due to method assignment during patching

There was issue #5062, which was closed as a duplicate in favor of this issue, which is shown as fixed. However, I am currently using Python 3.11.4 with mypy 1.4.1 and still getting the errors with ConfigParser, described in this comment - #5062 (comment). Is this expected, or duplicate issue was closed by mistake, and the error with ConfigParser is not fixed?

mypy wrongly checks type for attribute function assigment - updating …

Correct type hint at Context.function using Protocol

Navigation Menu

Repository navigation

Cannot assign to field of Callable type #708

62 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Cannot assign to field of Callable type #708

Description

Activity

spkersten commented on Jun 6, 2015

JukkaL commented on Jun 7, 2015

JukkaL commented on Jun 7, 2015

spkersten commented on Jun 7, 2015

tharvik commented on Jul 29, 2016

gvanrossum commented on Jul 29, 2016

gnprice commented on Aug 4, 2016

gnprice commented on Aug 4, 2016

tharvik commented on Aug 5, 2016

gvanrossum commented on Aug 5, 2016

62 remaining items

kerimovkhikmet commented on Aug 8, 2023

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions