Kivy循环生成MD List项绑定函数参数异常问题求助

我基于Python+SQLite+Kivy开发密码管理器，密码列表页通过MDList展示所有密码项，点击任意项应进入对应详情页执行编辑/删除/复制操作，但实际点击后详情页标签始终显示列表最后一项的名称。

循环生成OneLineListItem时，每个项绑定了go_to_chosen_password(i)，但所有点击事件都使用了循环结束时i的最终值，导致显示错误。

问题根源 #

Lambda表达式在循环中采用延迟绑定机制：它不会在定义时捕获循环变量i的当前值，而是在触发点击事件时才去读取i的当前引用。循环结束后，i指向列表最后一个元素，因此所有点击事件都会传入这个值。

修复方案 #

方案1：Lambda添加默认参数捕获当前值 #

通过给lambda设置默认参数，强制在循环时捕获i的当前快照：

class PasswordsMenuScreen(Screen):
    # 导入get_list_of_passwords逻辑

    def on_enter(self):
        self.list_of_pass = get_list_of_passwords(...)

        for i in self.list_of_pass:
            self.item = OneLineListItem(text=i)
            # 用默认参数passw=i捕获当前循环的i值，避免延迟绑定
            self.item.bind(on_press=lambda x, passw=i: self.go_to_chosen_password(passw))
            self.ids.pass_list.add_widget(self.item)

    def go_to_chosen_password(self, passw):
        target_screen = self.manager.get_screen('chosen_password_screen')
        target_screen.ids.name.text = passw
        self.manager.transition.direction = 'right'
        self.manager.current = 'chosen_password_screen'


class ChosenPasswordScreen(Screen):
    pass

方案2：使用functools.partial显式绑定参数 #

借助functools.partial提前固定函数参数，可读性更强：
首先导入partial：

from functools import partial

然后修改循环绑定逻辑：

class PasswordsMenuScreen(Screen):
    # 导入get_list_of_passwords逻辑

    def on_enter(self):
        self.list_of_pass = get_list_of_passwords(...)

        for i in self.list_of_pass:
            self.item = OneLineListItem(text=i)
            # 用partial绑定当前i到函数参数，显式固定值
            self.item.bind(on_press=partial(self.go_to_chosen_password, i))
            self.ids.pass_list.add_widget(self.item)

    def go_to_chosen_password(self, passw, *args):
        # 注意：bind会额外传递触发事件的控件对象，所以需要用*args接收
        target_screen = self.manager.get_screen('chosen_password_screen')
        target_screen.ids.name.text = passw
        self.manager.transition.direction = 'right'
        self.manager.current = 'chosen_password_screen'


class ChosenPasswordScreen(Screen):
    pass

补充说明 #

• 方案1利用Python默认参数的定义时求值特性，把当前i的状态保存下来，规避延迟绑定问题，代码改动最小。
• 方案2通过partial包装函数，提前锁定参数值，适合参数较多或逻辑复杂的场景，代码可读性更高。

原界面布局代码（design.kv） #

<PasswordsMenuScreen>:
 canvas.before:
  Color:
   rgba: (0, 0, 1, 1)
  Rectangle:
   pos: self.pos
   size: self.size
 GridLayout:
  cols: 1
  Label:
   text: 'Passwords Lab'
   font_size: '35sp'
   size_hint_y: None
   height: 150
   size_hint_x: None
   width: 1500
  GridLayout:
   cols: 2
   padding: 15, 15
   spacing: 20, 20
   GridLayout:
    cols: 2
    ScrollView:
     MDList:
      id: pass_list
      font_size: '23sp'
    Button:
     text: '+'
     size_hint_y: None
     height: 80
     size_hint_x: None
     width: 80
     on_press: root.go_to_adding_password_menu()
  GridLayout:
   cols: 1
   size_hint: 0.2, 0.15
   padding: 10, 10
   spacing: 10, 0
   Button:
    text: 'Main Menu'
    background_color: 1, 1, 1, 0
    opacity: 1 if self.state == 'normal' else 0.5
    color: 0.1, 0.7, 1, 1
    on_press: root.go_to_main_menu()

<ChosenPasswordScreen>:
 canvas.before:
  Color:
   rgba: (0, 0, 1, 1)
  Rectangle:
   pos: self.pos
   size: self.size
 GridLayout:
  cols: 1
  GridLayout:
   cols: 1
   padding: 15, 15
   spacing: 30, 30
   Label:
    id: name
    text: ''
    font_size: '35sp'
   GridLayout:
    cols: 1
    padding: 25, 25
    spacing: 30, 30
    Label:
     text: 'Login'
     font_size: '20sp'
    TextInput:
     id: login
     size_hint: 1, 0.5
    Label:
     text: 'Password'
     font_size: '20sp'
    TextInput:
     id: password
     size_hint: 1, 0.5
   GridLayout:
    cols: 2
    Button:
     text: 'Edit'
     size_hint: 0.2, 0.4
     pos_hint: {'center_x': 0.5, 'center_y': 0.6}
    Button:
     text: 'Delete'
     size_hint: 0.2, 0.4
     pos_hint: {'center_x': 0.5, 'center_y': 0.6}
  GridLayout:
   cols: 1
   size_hint: 0.2, 0.2 # 20% of window space
   padding: 10, 10
   spacing: 10, 0
   Button:
    text: 'Back'
    background_color: 0, 1, 1, 0
    opacity: 1 if self.state == 'normal' else 0.5
    color: 0.1, 0.7, 1, 1
    on_press: root.go_back_to_passwords_menu()

内容的提问来源于stack exchange，提问作者Nikola Tesla