I think one of the reasons that del has its own syntax is that replacing it with a function might be hard in certain cases given it operates on the binding or variable and not the value it references. Thus if a function version of del were to be created a context would need to be passed in. del foo would need to become globals().remove('foo') or locals().remove('foo') which gets messy and less readable. Still I say getting rid of del would be good given its seemingly rare use. But removing language features/flaws can be painful. Maybe python 4 will remove it :)

使用numpy.load后强制关闭文件:

这可能是一个小众的用法，但我发现它在使用numpy时很有用。加载以读取文件。每隔一段时间，我就会更新文件，需要复制一个同名的文件到目录中。

我使用del来释放文件，并允许我复制新文件。

注意，我想避免使用with context管理器，因为我在命令行上玩图，不想经常按tab键!

看这个问题。

还有一个小众用途: 在带有ROOT5或ROOT6的pyroot中，"del"可以用于删除引用不再存在的c++对象的python对象。这允许pyroot的动态查找找到同名的c++对象，并将其绑定到python名称。所以你可以有这样一个场景:

import ROOT as R
input_file = R.TFile('inputs/___my_file_name___.root')
tree = input_file.Get('r')
tree.Draw('hy>>hh(10,0,5)')
R.gPad.Close()
R.hy # shows that hy is still available. It can even be redrawn at this stage.
tree.Draw('hy>>hh(3,0,3)') # overwrites the C++ object in ROOT's namespace
R.hy # shows that R.hy is None, since the C++ object it pointed to is gone
del R.hy
R.hy # now finds the new C++ object

希望ROOT7的更健全的对象管理能够填补这个空缺。

我发现del有用的一个地方是清除for循环中的无关变量:

for x in some_list:
  do(x)
del x

现在你可以确定，如果你在for循环之外使用x，它将是没有定义的。

del is the equivalent of "unset" in many languages and as a cross reference point moving from another language to python.. people tend to look for commands that do the same thing that they used to do in their first language... also setting a var to "" or none doesn't really remove the var from scope..it just empties its value the name of the var itself would still be stored in memory...why?!? in a memory intensive script..keeping trash behind its just a no no and anyways...every language out there has some form of an "unset/delete" var function..why not python?

只是另一种想法。

当在Django这样的框架中调试http应用程序时，调用堆栈中充满了以前使用过的无用和混乱的变量，特别是当它是一个非常长的列表时，这对开发人员来说是非常痛苦的。因此，在这一点上，名称空间控制可能是有用的。