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

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

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

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

看这个问题。

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 :)

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

for x in some_list:
  do(x)
del x

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

当你使用sys.exc_info()检查异常时，有一个特定的例子说明你应该使用del(可能还有其他的例子，但我知道这个是现成的)。这个函数返回一个元组、引发的异常类型、消息和一个回溯。

前两个值通常足以诊断错误并对其进行处理，但第三个值包含从引发异常的位置到捕获异常的位置之间的整个调用堆栈。特别是，如果你做

try:
    do_evil()
except:
    exc_type, exc_value, tb = sys.exc_info()
    if something(exc_value):
        raise

回溯，TB最终在调用堆栈的局部变量中，创建了一个不能被垃圾收集的循环引用。因此，重要的是要做到:

try:
    do_evil()
except:
    exc_type, exc_value, tb = sys.exc_info()
    del tb
    if something(exc_value):
        raise

打破循环引用。在许多情况下，您希望调用sys.exc_info()，就像使用元类魔法一样，回溯是有用的，因此您必须确保在可能离开异常处理程序之前清除它。如果你不需要回溯，你应该立即删除它，或者直接执行:

exc_type, exc_value = sys.exc_info()[:2]

一起避免这一切。

我想详细说明公认的答案，以强调将变量设置为None与使用del删除变量之间的细微差别:

给定变量foo = 'bar'，函数定义如下:

def test_var(var):
    if var:
        print('variable tested true')
    else:
        print('variable tested false')

一旦初始声明，test_var(foo)产生的变量测试为true。

现在试一试:

foo = None
test_var(foo)

它产生的变量测试为假。

将这种行为与以下行为进行对比:

del foo
test_var(foo)

现在会引发NameError: name 'foo'没有定义。

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?