First I just want to say I really like to use Pyclewn in Vim. It's probably the best way to debug python code anywhere.
One problem I found with Pyclewn, however, is that it looks like running pdb in pyclewn is much slower than running plain pdb. For example, I have code like this: import time def main(): #import pdb; pdb.set_trace() t = time.time() for i in xrange(300000): i * i x = time.time() - t print x return if __name__ == '__main__': main() Say you save this to a test.py. If I do a ":Pyclewn pdb test.py" in Vim and I set a break point on the line with "print x", I would get something like: 5.09845495224 If, however, I uncomment the pdb line, run "python test.py" on the command-line WITHOUT Vim, set a break at "print x", and run till the break point, I would get x as: 2.14030194283 It looks like Pyclewn is 2 times slower! I'm running this on 64-bit python on Linux. Nothing in the code seems really weird to me. I'm just wondering what Pyclewn is doing to make the python code run much slower than usual. So far, I have been using Pyclewn only on small code. The performance problem becomes much more serious on large projects. Is there something that I can do to speed this up? Thanks! Will ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
