开发者社区> 吞吞吐吐的> 正文
阿里云
为了无法计算的价值
打开APP
阿里云APP内打开

Python代码调试

简介:
+关注继续查看

 原来不怎么喜欢调试,写的程序大了,感觉调试也是很有必要的,简单总结一下几种常用的调试方式

1.print输出

  不要小看print输出,有时候,或许这是最快的方式。通过print将某个变量的值输出,再和预期的值进行比较,有问题的话再去分析源码看看哪里有错误。

2.logging模块

  这个模块比较强大,也很有用,完全可以替代print。logging模块可以定义日志级别,包括NOTSET < DEBUG < INFO < WARNING < ERROR < CRITICAL这几个级别,通过设置可以输出某个级别以上的日志,可以选择将日志保存到文件或者在屏幕输出。具体用法可以参考python手册

3.用bpython编写代码

  这个编辑器的优点是写完一行代码之后立即执行,然后我们能立即看到结果,出现问题可以及时撤销代码,编写完成可以将代码保存。代码提示功能也挺强大的。

4.用python -i来执行代码

  这样执行之后,程序并没有立即退出。而是打开一个python交互式命令行界面,在这里我们可以执行一些命令,比如 dir() 来查看变量和函数,直接输入变量名我们就能查看变量的值。如果程序异常退出的话,也会保留“现场”,我们可以从现场来分析,找到错误。

5.pdb调试

  最后讲这个神器。

  看了一下官方文档,pdb模块是用bdp模块和cmd模块来实现的。实现类似pdb的功能。

  使用这个模块的话简单的方法就是设置断点,先倒入pdb模块,然后在需要停下的地方执行pdb.set_trace()命令,这样程序执行到这个命令的时候就会停下来,然后我们就能输入一些pdb命令来进行调试了。可以单步执行,继续执行,可以查看变量的值,可以执行一些语句,可以显示将要执行的代码块,可以让程序跳转,执行另外的语句。

  详细的命令可以参考官方文档:

复制代码
h(elp) [command]
Without argument, print the list of available commands. With a command as argument, print help about that command. help pdb displays the full documentation file; if the environment variable PAGER is defined, the file is piped through that command instead. Since thecommand argument must be an identifier, help exec must be entered to get help on the ! command.
w(here)
Print a stack trace, with the most recent frame at the bottom. An arrow indicates the current frame, which determines the context of most commands.
d(own)
Move the current frame one level down in the stack trace (to a newer frame).
u(p)
Move the current frame one level up in the stack trace (to an older frame).
b(reak) [[filename:]lineno | function[, condition]]
With a lineno argument, set a break there in the current file. With a function argument, set a break at the first executable statement within that function. The line number may be prefixed with a filename and a colon, to specify a breakpoint in another file (probably one that hasn’t been loaded yet). The file is searched on sys.path. Note that each breakpoint is assigned a number to which all the other breakpoint commands refer.
If a second argument is present, it is an expression which must evaluate to true before the breakpoint is honored.
Without argument, list all breaks, including for each breakpoint, the number of times that breakpoint has been hit, the current ignore count, and the associated condition if any.
tbreak [[filename:]lineno | function[, condition]]
Temporary breakpoint, which is removed automatically when it is first hit. The arguments are the same as break.
cl(ear) [filename:lineno | bpnumber [bpnumber ...]]
With a filename:lineno argument, clear all the breakpoints at this line. With a space separated list of breakpoint numbers, clear those breakpoints. Without argument, clear all breaks (but first ask confirmation).
disable [bpnumber [bpnumber ...]]
Disables the breakpoints given as a space separated list of breakpoint numbers. Disabling a breakpoint means it cannot cause the program to stop execution, but unlike clearing a breakpoint, it remains in the list of breakpoints and can be (re-)enabled.
enable [bpnumber [bpnumber ...]]
Enables the breakpoints specified.
ignore bpnumber [count]
Sets the ignore count for the given breakpoint number. If count is omitted, the ignore count is set to 0. A breakpoint becomes active when the ignore count is zero. When non-zero, the count is decremented each time the breakpoint is reached and the breakpoint is not disabled and any associated condition evaluates to true.
condition bpnumber [condition]
Condition is an expression which must evaluate to true before the breakpoint is honored. If condition is absent, any existing condition is removed; i.e., the breakpoint is made unconditional.
commands [bpnumber]
Specify a list of commands for breakpoint number bpnumber. The commands themselves appear on the following lines. Type a line containing just ‘end’ to terminate the commands. An example:
(Pdb) commands 1
(com) print some_variable
(com) end
(Pdb)
To remove all commands from a breakpoint, type commands and follow it immediately with end; that is, give no commands.
With no bpnumber argument, commands refers to the last breakpoint set.
You can use breakpoint commands to start your program up again. Simply use the continue command, or step, or any other command that resumes execution.
Specifying any command resuming execution (currently continue, step, next, return, jump, quit and their abbreviations) terminates the command list (as if that command was immediately followed by end). This is because any time you resume execution (even with a simple next or step), you may encounter another breakpoint–which could have its own command list, leading to ambiguities about which list to execute.
If you use the ‘silent’ command in the command list, the usual message about stopping at a breakpoint is not printed. This may be desirable for breakpoints that are to print a specific message and then continue. If none of the other commands print anything, you see no sign that the breakpoint was reached.
New in version 2.5.
s(tep)
Execute the current line, stop at the first possible occasion (either in a function that is called or on the next line in the current function).
n(ext)
Continue execution until the next line in the current function is reached or it returns. (The difference between next and step is that stepstops inside a called function, while next executes called functions at (nearly) full speed, only stopping at the next line in the current function.)
unt(il)
Continue execution until the line with the line number greater than the current one is reached or when returning from current frame.
New in version 2.6.
r(eturn)
Continue execution until the current function returns.
c(ont(inue))
Continue execution, only stop when a breakpoint is encountered.
j(ump) lineno
Set the next line that will be executed. Only available in the bottom-most frame. This lets you jump back and execute code again, or jump forward to skip code that you don’t want to run.
It should be noted that not all jumps are allowed — for instance it is not possible to jump into the middle of a for loop or out of afinally clause.
l(ist) [first[, last]]
List source code for the current file. Without arguments, list 11 lines around the current line or continue the previous listing. With one argument, list 11 lines around at that line. With two arguments, list the given range; if the second argument is less than the first, it is interpreted as a count.
a(rgs)
Print the argument list of the current function.
p expression
Evaluate the expression in the current context and print its value.
Note print can also be used, but is not a debugger command — this executes the Python print statement.
pp expression
Like the p command, except the value of the expression is pretty-printed using the pprint module.
alias [name [command]]
Creates an alias called name that executes command. The command must not be enclosed in quotes. Replaceable parameters can be indicated by %1, %2, and so on, while %* is replaced by all the parameters. If no command is given, the current alias for name is shown. If no arguments are given, all aliases are listed.
Aliases may be nested and can contain anything that can be legally typed at the pdb prompt. Note that internal pdb commands can be overridden by aliases. Such a command is then hidden until the alias is removed. Aliasing is recursively applied to the first word of the command line; all other words in the line are left alone.
As an example, here are two useful aliases (especially when placed in the .pdbrc file):
#Print instance variables (usage "pi classInst")
alias pi for k in %1.__dict__.keys(): print "%1.",k,"=",%1.__dict__[k]
#Print instance variables in self
alias ps pi self
unalias name
Deletes the specified alias.
[!]statement
Execute the (one-line) statement in the context of the current stack frame. The exclamation point can be omitted unless the first word of the statement resembles a debugger command. To set a global variable, you can prefix the assignment command with a global command on the same line, e.g.:
(Pdb) global list_options; list_options = ['-l']
(Pdb)
run [args ...]
Restart the debugged Python program. If an argument is supplied, it is split with “shlex” and the result is used as the new sys.argv. History, breakpoints, actions and debugger options are preserved. “restart” is an alias for “run”.
New in version 2.6.
q(uit)
Quit from the debugger. The program being executed is aborted.
复制代码

 


本文转自ma6174博客园博客,原文链接:http://www.cnblogs.com/ma6174/archive/2013/01/18/2865091.html,如需转载请自行联系原作者

版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。

相关文章
Python调试技巧
Python调试技巧
0 0
你真的会调试你的python程序吗?
你真的会调试你的python程序吗?
0 0
利用PySnooper进行Python代码调试
利用PySnooper进行Python代码调试
0 0
我常用的Python调试工具
以下是我做调试或分析时用过的工具的一个概览。如果你知道有更好的工具,请在评论中留言,可以不用很完整的介绍。
0 0
python 调试技巧
文章说明 编程过程中,出现BUG不可避免,所以经常要进行调试. 在廖雪峰的python3教程中,有一篇专门讲调试的文章,简单列举了调试的几种方法,建议先进行阅读,了解一下。
1054 0
在IE中使用Python作为开发脚本
在IE中使用Python作为开发脚本 目前IE支持的客户端脚本语言常见的有VBScript和JavaScript,这两种脚本语言在操作页面元素方面基本能满足一般应用的需要,可通过和COM集成来获得扩展功能。
413 0
python的调试
在python脚本中可以用pdb进行调试,具体方法如下: 1.使用run语句调试,格式为: run(statement[,globals[,locals]]) 参数含义如下 statement:要调试的语句块,以字符串的形式globals:可选参数,设置statement运行的全局环境变量l...
487 0
文章
问答
文章排行榜
最热
最新
相关电子书
更多
Python 脚本速查手册
立即下载
Python系列直播第一讲——Python中的一切皆对象
立即下载
Python第五讲——关于爬虫如何做js逆向的思路
立即下载