嵌套 try/catch 语句是否不好？
我现在的情况：
try:
try:
condition
catch
try:
condition
catch
catch
major failure
这样的代码是不是很糟糕？它是否太混乱了，或者类似的事情意味着什么？
My case right now:
try:
try:
condition
catch
try:
condition
catch
catch
major failure
Is it bad to have the code like that? Does it clutter too much, or what are the implications of something like that?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不，这有点常见（除了关键字是
except而不是catch）。这取决于您需要做什么和设计。我看到太多的坏处是捕获顶级 Exception 类，而不是更具体的东西（例如 KeyError）。或者提高同样的。
No, that's somewhat common (except the keyword is
exceptrather thancatch). It depends on what you need to do and the design.What IS bad, that I see too much of, is catching top-level
Exceptionclass, rather than something more specific (e.g. KeyError). Or raising the same.我不会只是做出结论并声称“这很糟糕”，因为有时你可能需要它。 Python 有时会故意抛出异常，而不是让你问（这是……吗？）[EAFP 座右铭]，并且在某些情况下，
try/catch的嵌套很有用 - 当这对逻辑流程有意义时的代码。但我的猜测是，大多数时候你不会。因此，针对您的情况，更好的问题是提出您认为需要此类代码的特定用例。
I wouldn't just cut a verdict and claim "it's bad", because sometimes you may need it. Python sometimes deliberately throws exceptions instead of letting you ask (does this ...?) [the EAFP motto] and in some cases nesting of
try/catchis useful - when this makes sense with the logical flow of the code.But my guess is that most times you don't. So a better question in your case would be to present a specific use case where you think you need such code.