如何警告类(名称)弃用
我已经重命名了一个属于库一部分的 python 类。我愿意保留使用其以前的名称一段时间的可能性,但想警告用户它已被弃用并将在将来被删除。
我认为为了提供向后兼容性,使用这样的别名就足够了:
class NewClsName:
pass
OldClsName = NewClsName
我不知道如何以优雅的方式将 OldClsName
标记为已弃用。也许我可以使 OldClsName
成为一个向日志发出警告的函数,并从其参数构造 NewClsName
对象(使用 *args
和 < code>**kvargs),但它看起来不够优雅(或者也许是?)。
但是,我不知道 Python 标准库弃用警告是如何工作的。我想可能有一些很好的魔法来处理弃用,例如允许根据某些解释器的命令行选项将其视为错误或沉默。
问题是:如何警告用户使用过时的类别名(或一般情况下过时的类)。
编辑:函数方法对我不起作用(我已经尝试过),因为该类有一些类方法(工厂方法),当 OldClsName< /code> 被定义为一个函数。以下代码不起作用:
class NewClsName(object):
@classmethod
def CreateVariant1( cls, ... ):
pass
@classmethod
def CreateVariant2( cls, ... ):
pass
def OldClsName(*args, **kwargs):
warnings.warn("The 'OldClsName' class was renamed [...]",
DeprecationWarning )
return NewClsName(*args, **kwargs)
OldClsName.CreateVariant1( ... )
因为:
AttributeError: 'function' object has no attribute 'CreateVariant1'
继承是我唯一的选择吗?老实说,它对我来说看起来不太干净——它通过引入不必要的派生来影响类层次结构。此外,OldClsName 不是 NewClsName
这在大多数情况下不是问题,但如果使用该库的代码编写得不好,则可能会出现问题。
我还可以创建一个虚拟的、不相关的 OldClsName
类,并实现一个构造函数以及其中所有类方法的包装器,但在我看来,这是更糟糕的解决方案。
I have renamed a python class that is part of a library. I am willing to leave a possibility to use its previous name for some time but would like to warn user that it's deprecated and will be removed in the future.
I think that to provide backward compatibility it will be enough to use an alias like that:
class NewClsName:
pass
OldClsName = NewClsName
I have no idea how to mark the OldClsName
as deprecated in an elegant way. Maybe I could make OldClsName
a function which emits a warning (to logs) and constructs the NewClsName
object from its parameters (using *args
and **kvargs
) but it doesn't seem elegant enough (or maybe it is?).
However, I don't know how Python standard library deprecation warnings work. I imagine that there may be some nice magic to deal with deprecation, e.g. allowing treating it as errors or silencing depending on some interpreter's command line option.
The question is: How to warn users about using an obsolete class alias (or obsolete class in general).
EDIT: The function approach doesn't work for me (I already gave it a try) because the class has some class methods (factory methods) which can't be called when the OldClsName
is defined as a function. Following code won't work:
class NewClsName(object):
@classmethod
def CreateVariant1( cls, ... ):
pass
@classmethod
def CreateVariant2( cls, ... ):
pass
def OldClsName(*args, **kwargs):
warnings.warn("The 'OldClsName' class was renamed [...]",
DeprecationWarning )
return NewClsName(*args, **kwargs)
OldClsName.CreateVariant1( ... )
Because of:
AttributeError: 'function' object has no attribute 'CreateVariant1'
Is inheritance my only option? To be honest, it doesn't look very clean to me - it affects class hierarchy through introduction of unnecessary derivation. Additionally, OldClsName is not NewClsName
what is not an issue in most cases but may be a problem in case of poorly written code using the library.
I could also create a dummy, unrelated OldClsName
class and implement a constructor as well as wrappers for all class methods in it, but it is even worse solution, in my opinion.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(7)
是的,我认为这是相当标准的做法:
唯一棘手的事情是,如果您有从
OldClsName
子类化的东西 - 那么我们必须变得聪明。如果您只需要保留对类方法的访问,这应该可以做到:我还没有测试过它,但这应该给您这个想法 -
__call__
将处理正常实例路由,__getattr__
将捕获对类方法和类方法的访问。仍然会生成警告,而不会扰乱您的班级层次结构。Yup, I think that's pretty standard practice:
The only tricky thing is if you have things that subclass from
OldClsName
- then we have to get clever. If you just need to keep access to class methods, this should do it:I haven't tested it, but that should give you the idea -
__call__
will handle the normal-instantation route,__getattr__
will capture accesses to the class methods & still generate the warning, without messing with your class heirarchy.请查看
warnings.warn
。正如您将看到的,文档中的示例是弃用警告:
Please have a look at
warnings.warn
.As you'll see, the example in the documentation is a deprecation warning:
在 python >= 3.6 中,您可以轻松处理子类化警告:
重载 __new__ 应该允许您在直接调用旧类构造函数时发出警告,但我没有测试过,因为我不需要就现在。
In python >= 3.6 you can easily handle warning on subclassing:
Overloading
__new__
should allow you to warn when the old class constructor is called directly, but I haven't tested that since I don't need it right now.以下是解决方案应满足的要求列表:
isinstance
和issubclass
检查解决方案
此可以使用自定义元类来实现:
说明
DeprecatedClassMeta.__new__
方法不仅会为它是其元类的类调用,还会为该类的每个子类调用。这提供了一个机会来确保DeprecatedClass
的任何实例都不会被实例化或子类化。实例化很简单。元类重写
__new__
方法DeprecatedClass
始终返回NewClass
的实例。子类化并不困难。
DeprecatedClassMeta.__new__
接收基类列表,需要用NewClass
替换DeprecatedClass
的实例。最后,
isinstance
和issubclass
检查是通过 PEP 3119。测试
Here is the list of requirements a solution should satisfy:
isinstance
andissubclass
checksSolution
This can be achieved with a custom metaclass:
Explanation
DeprecatedClassMeta.__new__
method is called not only for a class it is a metaclass of but also for every subclass of this class. That gives an opportunity to ensure that no instance ofDeprecatedClass
will ever be instantiated or subclassed.Instantiation is simple. The metaclass overrides the
__new__
method ofDeprecatedClass
to always return an instance ofNewClass
.Subclassing is not much harder.
DeprecatedClassMeta.__new__
receives a list of base classes and needs to replace instances ofDeprecatedClass
withNewClass
.Finally, the
isinstance
andissubclass
checks are implemented via__instancecheck__
and__subclasscheck__
defined in PEP 3119.Test
从 Python 3.7 开始,您可以使用
__getattr__
(和__dir__
)提供模块属性访问的自定义。一切都在 PEP 562 中进行了解释。在下面的示例中,我实现了
__getattr__
和__dir__
以便弃用“OldClsName”,转而使用“NewClsNam”:在
__getattr__
函数中,如果发现已弃用的类或函数名称,则会发出警告消息,显示调用者的源文件和行号(使用stacklevel=2
)。在用户代码中,我们可以:
当用户运行他的脚本
your_lib_usage.py
时,它将得到如下内容:注意: 堆栈跟踪通常以 STDERR 编写。
要查看错误警告,您可能需要在 Python 命令行中添加“-W”标志,例如:
Since Python 3.7, you can provide a customization of module attribute access using
__getattr__
(and__dir__
). Everything is explained in PEP 562.In the bellow example, I implemented
__getattr__
and__dir__
in order to deprecate the “OldClsName” in favor of “NewClsNam”:In the
__getattr__
function, if a deprecated class or function name is found, a warning message is emitted, showing the source file and line number of the caller (withstacklevel=2
).In the user code, we could have:
When the user run his script
your_lib_usage.py
, it will get something like this:Note: the stack trace is usually written in STDERR.
To see the error warnings, you may need to add a “-W” flag in the Python command line, for instance:
你为什么不直接子类化呢?这样就不会破坏用户代码。
Why don't you just sub-class? This way no user code should be broken.
使用
inspect
模块为OldClass
添加占位符,然后OldClsName is NewClsName
检查将通过,并且像 pylint 这样的 linter 会将其告知为错误。deprecate.py
test.py
然后运行 python -W all test.py :
Use
inspect
module to add placeholder forOldClass
, thenOldClsName is NewClsName
check will pass, and a linter like pylint will inform this as error.deprecate.py
test.py
then run
python -W all test.py
: