Python中单下划线变量的作用及PyQt代码中(,_)的含义问询
Hey there! Let’s tackle your two Python/PyQt questions step by step—they’re both super common once you start digging into Python’s conventions and PyQt’s internals.
1. What’s the deal with single-underscore variables in Python?
Single underscores (_) have a few key uses depending on the context:
- "Internal use only" hint: It’s a widely accepted convention to mark variables, functions, or class methods as intended for internal use (within a module or class). Python doesn’t actually block external code from accessing them, but it’s a clear signal to other developers that messing with these elements might break things.
- Discarding values during unpacking: This is exactly what’s happening in your PyQt code! When a function returns multiple values you don’t all need, using
_lets you "throw away" the ones you don’t care about cleanly—way better than assigning them to a random variable name you’ll never use. - REPL shortcut: In Python’s interactive shell,
_automatically holds the result of the last expression you ran. Perfect for when you forget to assign a value to a variable and want to reuse it quickly.
2. What does (,_) mean in your loadUiType line, and why does removing it cause that error?
Let’s break this down:
First, what does loadUiType do? This PyQt function returns two separate values when you call it:
- The generated UI class (this is what you store in
FROM_CLASS—you’ll inherit from this later in your code) - A metaclass that PyQt uses under the hood to integrate the UI class with Qt’s framework. You don’t need to use this metaclass directly, but it’s part of the function’s return value.
When you write FROM_CLASS, _ = loadUiType(...), you’re using Python’s tuple unpacking to grab the first value (the UI class) and discard the second (the metaclass) with _.
Now, why the error when you remove ,_?
If you just do FROM_CLASS = loadUiType(...), you’re assigning the entire tuple of two values to FROM_CLASS instead of just the first one. Later, when you try to create a class that inherits from FROM_CLASS (like class MyApp(FROM_CLASS, QMainWindow):), Python gets confused—because FROM_CLASS is a tuple, not a single class. This leads to the metaclass conflict error, since Python can’t figure out the correct metaclass to use for your derived class when it’s given a tuple instead of a proper base class.
In short: the ,_ is necessary to properly split the two return values—you keep the one you need, and toss the other with _ since you don’t have to work with it directly.
内容的提问来源于stack exchange，提问作者Qais Bsharat
