Hey there! Let's tackle your Tkinter issues step by step—since you're building a GUI for Raspberry Pi and hitting that frustrating 'object has no attribute' error, plus wondering about best practices for structuring your app.

You mentioned you suspect the issue is related to formatting, which makes sense—Python's strict syntax (especially around indentation) is a common culprit here. Here are the most likely format-related causes to check:

• Indentation mistakes
  Python uses indentation to define code blocks, so if a method or attribute isn't properly indented inside your class, it won't be part of the class instance. For example:

  Wrong:

  class Application(tk.Tk):
  def __init__(self):  # Indentation doesn't match the class
      super().__init__()
  
  def create_buttons():  # This is outside the class's scope!
      self.btn = tk.Button(self, text="Click")
  

  Correct:

  class Application(tk.Tk):
      def __init__(self):  # Properly indented under the class
          super().__init__()
          self.create_buttons()
  
      def create_buttons():  # Indented to belong to the class
          self.btn = tk.Button(self, text="Click")
  

• Typos in names
  It's easy to misspell a method or attribute name (e.g., self.status_lbl vs self.status_label when you defined it). Double-check every reference to self.xxx matches the exact name you used when creating the attribute or method.

• Missing self for instance attributes
  If you create a widget or variable inside a method but forget to prefix it with self, it's only a local variable in that method—not part of the class instance. Later, when you try to access it with self.widget_name, Python won't find it. For example:

  def setup_ui(self):
      label = tk.Label(self, text="Hello")  # No self—local variable only
      label.pack()
  # Later, trying self.label will throw the error!
  

• Incorrect parent widget assignment
  In Tkinter, when creating a widget, always pass self as the parent (unless you intend it to be a child of another widget). If you skip this, the widget might not bind properly to your class instance, leading to unexpected attribute errors if you try to reference it later.

Absolutely—using an Application class (usually inheriting from tk.Tk or tk.Frame) is a standard, recommended best practice for Tkinter development, especially for apps you plan to use or expand on. Here's why:

• Clean organization: It wraps all your UI elements, event handlers, and app logic in one place, instead of scattering code across global variables and random functions.
• Easier maintenance: When you need to tweak a feature or fix a bug, all related code lives within the class, so you don't have to hunt through a messy script.
• Reusability: You can extend the class, or extract components (like a custom input frame) into their own classes that work seamlessly with your main Application.
• Simpler event handling: Using class methods as callbacks avoids messy workarounds like global variables, since the method has access to all instance attributes via self.

That said, for throwaway test scripts (like a single window with one button), a procedural approach might work. But for any serious GUI on your Raspberry Pi, the class-based Application pattern is the way to go.

内容的提问来源于stack exchange，提问作者Zefrin Cochran