Why does += behave unexpectedly on lists?(为什么 += 在列表中表现异常?)
问题描述
python 中的 += 运算符似乎在列表上意外运行.谁能告诉我这是怎么回事?
The += operator in python seems to be operating unexpectedly on lists. Can anyone tell me what is going on here?
class foo:
bar = []
def __init__(self,x):
self.bar += [x]
class foo2:
bar = []
def __init__(self,x):
self.bar = self.bar + [x]
f = foo(1)
g = foo(2)
print f.bar
print g.bar
f.bar += [3]
print f.bar
print g.bar
f.bar = f.bar + [4]
print f.bar
print g.bar
f = foo2(1)
g = foo2(2)
print f.bar
print g.bar
输出
[1, 2]
[1, 2]
[1, 2, 3]
[1, 2, 3]
[1, 2, 3, 4]
[1, 2, 3]
[1]
[2]
foo += bar 似乎会影响该类的每个实例,而 foo = foo + bar 似乎以我期望的方式运行.
foo += bar seems to affect every instance of the class, whereas foo = foo + bar seems to behave in the way I would expect things to behave.
+= 运算符称为复合赋值运算符".
The += operator is called a "compound assignment operator".
推荐答案
一般的答案是 += 尝试调用 __iadd__ 特殊方法,如果是'不可用它尝试使用 __add__ 代替.所以问题在于这些特殊方法之间的区别.
The general answer is that += tries to call the __iadd__ special method, and if that isn't available it tries to use __add__ instead. So the issue is with the difference between these special methods.
__iadd__ 特殊方法用于就地添加,即它改变它作用的对象.__add__ 特殊方法返回一个新对象,也用于标准 + 运算符.
The __iadd__ special method is for an in-place addition, that is it mutates the object that it acts on. The __add__ special method returns a new object and is also used for the standard + operator.
因此,当 += 运算符用于定义了 __iadd__ 的对象时,该对象会被原地修改.否则它将尝试使用普通的 __add__ 并返回一个新对象.
So when the += operator is used on an object which has an __iadd__ defined the object is modified in place. Otherwise it will instead try to use the plain __add__ and return a new object.
这就是为什么对于像列表这样的可变类型 += 会改变对象的值,而对于像元组、字符串和整数这样的不可变类型会返回一个新对象(a += b 等同于 a = a + b).
That is why for mutable types like lists += changes the object's value, whereas for immutable types like tuples, strings and integers a new object is returned instead (a += b becomes equivalent to a = a + b).
对于同时支持 __iadd__ 和 __add__ 的类型,因此您必须小心使用哪一种.a += b 将调用 __iadd__ 并改变 a,而 a = a + b 将创建一个新对象并将其分配给 a.它们不是同一个操作!
For types that support both __iadd__ and __add__ you therefore have to be careful which one you use. a += b will call __iadd__ and mutate a, whereas a = a + b will create a new object and assign it to a. They are not the same operation!
>>> a1 = a2 = [1, 2]
>>> b1 = b2 = [1, 2]
>>> a1 += [3] # Uses __iadd__, modifies a1 in-place
>>> b1 = b1 + [3] # Uses __add__, creates new list, assigns it to b1
>>> a2
[1, 2, 3] # a1 and a2 are still the same list
>>> b2
[1, 2] # whereas only b1 was changed
对于不可变类型(没有 __iadd__)a += b 和 a = a + b 是等价的.这就是让你可以在不可变类型上使用 += 的原因,这可能看起来是一个奇怪的设计决定,直到你考虑到否则你不能在像数字这样的不可变类型上使用 +=!
For immutable types (where you don't have an __iadd__) a += b and a = a + b are equivalent. This is what lets you use += on immutable types, which might seem a strange design decision until you consider that otherwise you couldn't use += on immutable types like numbers!
这篇关于为什么 += 在列表中表现异常?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:为什么 += 在列表中表现异常?
- python-m http.server 443--使用SSL? 2022-01-01
- 使用Heroku上托管的Selenium登录Instagram时,找不到元素';用户名'; 2022-01-01
- 如何将一个类的函数分成多个文件? 2022-01-01
- padding='same' 转换为 PyTorch padding=# 2022-01-01
- 如何在 Python 的元组列表中对每个元组中的第一个值求和? 2022-01-01
- 如何在 python3 中将 OrderedDict 转换为常规字典 2022-01-01
- pytorch 中的自适应池是如何工作的? 2022-07-12
- python check_output 失败,退出状态为 1,但 Popen 适用于相同的命令 2022-01-01
- 分析异常:路径不存在:dbfs:/databricks/python/lib/python3.7/site-packages/sampleFolder/data; 2022-01-01
- 沿轴计算直方图 2022-01-01
