Paul wrote: > Vim python interface bug. > > Between any consecutive python code invocations, for example: > > :py def x(): print "hello World" > > and: > > :py x() > > State, specific to the (main) python thread is discarded. For example, > any attempt to use sys.settrace() fails to provide the expected > results. > > The attached patch fixes this for at least one case. > > FYI. I was trying to test vim-python extension code and obtain code coverage > statistics using Ned Batchelder's covergae.py. > > I have just built this into my everyday Vim instance. I will update > this post to indicate any problems or (lack thereof).
Does this also need to be changed in the Python 3 interface? Or was it already working correctly there? -- God made machine language; all the rest is the work of man. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
