使用 getter 和 setter 的 Python 方式是什么?
我这样做是这样的:
def set_property(property,value):
def get_property(property):
或者
object.property = value
value = object.property
使用 getter 和 setter 的 pythonic 方法是什么?
I'm doing it like:
def set_property(property,value):
def get_property(property):
or
object.property = value
value = object.property
What's the pythonic way to use getters and setters?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(9)
试试这个: Python 属性
示例代码是:
Try this: Python Property
The sample code is:
“Pythonic”方式是不使用“getters”和“setters”,而是使用普通属性,就像问题演示的那样,以及
del
用于删除(但名称被更改以保护无辜...内置):如果稍后您想要修改设置和获取,您可以通过使用
property
装饰器来完成此操作,而无需更改用户代码:(每个装饰器用法会复制并更新之前的属性对象,因此请注意,每个设置、获取和删除函数/方法应该使用相同的名称。)
定义上述内容后,原来的设置、获取和删除代码是相同的:
你应该避免这种情况:
不起作用,因为您没有为属性将设置为的实例提供参数(通常是
self
),这将是:首先,上面的方法 其次,这重复了两个特殊方法,
__setattr__
和__getattr__
。第三,我们还有
setattr
和getattr
内置函数。@property
装饰器用于创建 getter 和 setter。例如,我们可以修改设置行为来限制所设置的值:
一般来说,我们希望避免使用
property
而只使用直接属性。这正是 Python 用户所期望的。遵循最不令人惊讶的规则,您应该尽力满足用户的期望,除非您有非常令人信服的理由相反。
演示
例如,假设我们需要对象的 protected 属性是 0 到 100 之间的整数,并防止其被删除,并使用适当的消息来通知用户其正确用法:(
请注意,
__init__
指的是到 self.protected_value ,但属性方法引用 self._protected_value ,这样__init__
通过公共 API 使用该属性,确保它。是“受保护的”。)和用法:
名称重要吗?
是的,他们确实。
.setter
和.deleter
复制原始属性。这允许子类正确修改行为而不改变父类中的行为。现在要使其起作用,您必须使用相应的名称:
我不确定这在哪里有用,但用例是如果您想要一个仅获取、设置和/或删除的属性。可能最好坚持语义上相同的属性具有相同的名称。
结论
从简单的属性开始。
如果您稍后需要有关设置、获取和删除的功能,您可以使用属性装饰器添加它。
避免使用名为
set_...
和get_...
的函数 - 这就是属性的用途。The "Pythonic" way is not to use "getters" and "setters", but to use plain attributes, like the question demonstrates, and
del
for deleting (but the names are changed to protect the innocent... builtins):If later, you want to modify the setting and getting, you can do so without having to alter user code, by using the
property
decorator:(Each decorator usage copies and updates the prior property object, so note that you should use the same name for each set, get, and delete function/method.)
After defining the above, the original setting, getting, and deleting code is the same:
You should avoid this:
Firstly, the above doesn't work, because you don't provide an argument for the instance that the property would be set to (usually
self
), which would be:Secondly, this duplicates the purpose of two special methods,
__setattr__
and__getattr__
.Thirdly, we also have the
setattr
andgetattr
builtin functions.The
@property
decorator is for creating getters and setters.For example, we could modify the setting behavior to place restrictions the value being set:
In general, we want to avoid using
property
and just use direct attributes.This is what is expected by users of Python. Following the rule of least-surprise, you should try to give your users what they expect unless you have a very compelling reason to the contrary.
Demonstration
For example, say we needed our object's protected attribute to be an integer between 0 and 100 inclusive, and prevent its deletion, with appropriate messages to inform the user of its proper usage:
(Note that
__init__
refers toself.protected_value
but the property methods refer toself._protected_value
. This is so that__init__
uses the property through the public API, ensuring it is "protected".)And usage:
Do the names matter?
Yes they do.
.setter
and.deleter
make copies of the original property. This allows subclasses to properly modify behavior without altering the behavior in the parent.Now for this to work, you have to use the respective names:
I'm not sure where this would be useful, but the use-case is if you want a get, set, and/or delete-only property. Probably best to stick to semantically same property having the same name.
Conclusion
Start with simple attributes.
If you later need functionality around the setting, getting, and deleting, you can add it with the property decorator.
Avoid functions named
set_...
andget_...
- that's what properties are for.使用
@property
和@attribute.setter
不仅可以帮助您使用“pythonic”方式,还可以在创建对象和更改对象时检查属性的有效性。通过这种方式,您实际上对客户端开发人员“隐藏”
_name
属性,并对 name 属性类型执行检查。请注意,通过遵循此方法,即使在启动期间也会调用 setter。所以:将导致:
但是:
Using
@property
and@attribute.setter
helps you to not only use the "pythonic" way but also to check the validity of attributes both while creating the object and when altering it.By this, you actually 'hide'
_name
attribute from client developers and also perform checks on name property type. Note that by following this approach even during the initiation the setter gets called. So:Will lead to:
But:
这是一个老问题,但这个话题非常重要并且始终是最新的。如果有人想要超越简单的 getters/setters,我写了一篇关于 python 中超级属性的文章,支持插槽、可观察性和减少样板代码。
这个类可以这样使用:
此代码将产生以下输出:
有关如何以及为什么的更多信息,请参见:https://mnesarco.github.io/blog/2020/07/23/python-metaprogramming-properties-on-steroids
This is an old question but the topic is very important and always current. In case anyone wants to go beyond simple getters/setters i have wrote an article about superpowered properties in python with support for slots, observability and reduced boilerplate code.
This class can be used like this:
This code will produce the following output:
More info about how and why here: https://mnesarco.github.io/blog/2020/07/23/python-metaprogramming-properties-on-steroids
属性非常有用,因为您可以将它们与赋值一起使用,但也可以包含验证。您可以在使用装饰器 @property 和 @.setter 来创建方法的地方看到此代码:
我在这篇文章中也写了更多详细信息:https://pythonhowtoprogram.com/how-to-create-getter-setter-class-属性-in-python-3/
Properties are pretty useful since you can use them with assignment but then can include validation as well. You can see this code where you use the decorator @property and also @<property_name>.setter to create the methods:
There are more details in this post I wrote about this as well: https://pythonhowtoprogram.com/how-to-create-getter-setter-class-properties-in-python-3/
您可以使用访问器/修改器(即
@attr.setter
和@property
),但最重要的是保持一致!如果您使用
@property
来简单地访问属性,例如使用它来访问每个*属性!使用
@property
访问某些属性并保留一些其他属性 public (即不带下划线的名称)而不使用访问器,这将是一种不好的做法,例如 do not do请注意,
self.b
这里没有显式访问器,即使它是公共的。与setters(或mutators)类似,请随意使用
@attribute.setter
,但保持一致! do 例如我很难猜测你的意图。一方面,你说
a
和b
都是公共的(它们的名称中没有前导下划线),所以理论上我应该被允许访问/变异(获取/设置) 两个都。但随后您仅为a
指定了一个显式变元,这告诉我也许我不应该能够设置b
。由于您提供了显式变元,我不确定缺少显式访问器 (@property
) 是否意味着我不应该能够访问这些变量中的任何一个,或者您只是在使用 <代码>@属性。*例外情况是,您明确希望使某些变量可访问或可变但不是两者,或者您希望在访问或更改属性时执行一些附加逻辑。这是我个人使用
@property
和@attribute.setter
的时候(否则公共属性没有显式的访问器/修改器)。最后,PEP8 和 Google 风格指南建议:
PEP8、为继承而设计 说:
另一方面,根据 Google 风格指南 Python 语言规则/属性 建议:
这种方法的优点:
和缺点:
You can use accessors/mutators (i.e.
@attr.setter
and@property
) or not, but the most important thing is to be consistent!If you're using
@property
to simply access an attribute, e.g.use it to access every* attribute! It would be a bad practice to access some attributes using
@property
and leave some other properties public (i.e. name without an underscore) without an accessor, e.g. do not doNote that
self.b
does not have an explicit accessor here even though it's public.Similarly with setters (or mutators), feel free to use
@attribute.setter
but be consistent! When you do e.g.It's hard for me to guess your intention. On one hand you're saying that both
a
andb
are public (no leading underscore in their names) so I should theoretically be allowed to access/mutate (get/set) both. But then you specify an explicit mutator only fora
, which tells me that maybe I should not be able to setb
. Since you've provided an explicit mutator I am not sure if the lack of explicit accessor (@property
) means I should not be able to access either of those variables or you were simply being frugal in using@property
.*The exception is when you explicitly want to make some variables accessible or mutable but not both or you want to perform some additional logic when accessing or mutating an attribute. This is when I am personally using
@property
and@attribute.setter
(otherwise no explicit acessors/mutators for public attributes).Lastly, PEP8 and Google Style Guide suggestions:
PEP8, Designing for Inheritance says:
On the other hand, according to Google Style Guide Python Language Rules/Properties the recommendation is to:
The pros of this approach:
and cons:
您可以使用魔术方法
__getattribute__
和__setattr__
。请注意,
__getattr__
和__getattribute__
不同。__getattr__
仅在未找到属性时调用。You can use the magic methods
__getattribute__
and__setattr__
.Be aware that
__getattr__
and__getattribute__
are not the same.__getattr__
is only invoked when the attribute is not found.