From b3a0353bf2bd3b21234a63dda9d2ac8601cbd002 Mon Sep 17 00:00:00 2001
From: David Peter <mail@david-peter.de>
Date: Thu, 20 Feb 2025 15:47:46 +0100
Subject: [PATCH] Use __kwdefaults__ instead of __module__

---
 .../red_knot_python_semantic/resources/mdtest/call/methods.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/crates/red_knot_python_semantic/resources/mdtest/call/methods.md b/crates/red_knot_python_semantic/resources/mdtest/call/methods.md
index d6deb2cf7a..7e9a17bda2 100644
--- a/crates/red_knot_python_semantic/resources/mdtest/call/methods.md
+++ b/crates/red_knot_python_semantic/resources/mdtest/call/methods.md
@@ -90,11 +90,11 @@ reveal_type(bound_method.__hash__)  # revealed: <bound method `__hash__` of `Met
 ```
 
 If an attribute is not available on the bound method object, it will be looked up on the underlying
-function object. We model this explicitly, which means that we can access `__module__` on bound
+function object. We model this explicitly, which means that we can access `__kwdefaults__` on bound
 methods, even though it is not available on `types.MethodType`:
 
 ```py
-reveal_type(bound_method.__module__)  # revealed: str
+reveal_type(bound_method.__kwdefaults__)  # revealed: @Todo(generics) | None
 ```
 
 ## Basic method calls on class objects and instances