atom feed10 messages in net.sourceforge.lists.jython-dev[Jython-dev] Identifying executed lin...
FromSent OnAttachments
Chris BurroughsMay 11, 2009 6:05 am 
Jim BakerMay 11, 2009 7:09 am 
nedbatchelderMay 11, 2009 8:16 am 
Jim BakerMay 11, 2009 11:15 am 
Ned BatchelderMay 11, 2009 5:12 pm 
Jim BakerMay 11, 2009 7:36 pm 
Philip JenveyMay 11, 2009 8:37 pm 
Moss PrescottMay 11, 2009 9:33 pm 
Jim BakerMay 11, 2009 10:52 pm 
Ned BatchelderMay 12, 2009 4:12 am 
Subject:[Jython-dev] Identifying executed lines in jython
From:Chris Burroughs (chri@gmail.com)
Date:May 11, 2009 6:05:23 am
List:net.sourceforge.lists.jython-dev

Most python coverage tools depend on the CPython co_lnotab implementation. For example, both Coverage and figleaf use code like this modeled on the stdlib dis and trace modules: byte_increments = [ord(c) for c in code.co_lnotab[0::2]] line_increments = [ord(c) for c in code.co_lnotab[1::2]]

The jython differences page <http://jython.sourceforge.net/docs/differences.html> says that this co_lnotab will probably never be supported. What is the recommended way for developers to determine which lines of jython code were executed? Have the co_lnotab support plans changed, or should the .class files be examined, or is there an alternative approach?

Thank you.

------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com