Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #78413 > unrolled thread
| Started by | Ned Batchelder <ned@nedbatchelder.com> |
|---|---|
| First post | 2014-09-27 08:08 -0400 |
| Last post | 2014-09-27 08:08 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Understanding co_lnotab Ned Batchelder <ned@nedbatchelder.com> - 2014-09-27 08:08 -0400
| From | Ned Batchelder <ned@nedbatchelder.com> |
|---|---|
| Date | 2014-09-27 08:08 -0400 |
| Subject | Re: Understanding co_lnotab |
| Message-ID | <mailman.14426.1411819753.18130.python-list@python.org> |
On 9/26/14 7:13 AM, Shiyao Ma wrote: > When reading the notes on co_lnotab > > I totally got lost at this > line:https://hg.python.org/cpython/file/fd0c02c3df31/Objects/lnotab_notes.txt#l31 > > It says,"In case #b, there's no way to know > from looking at the table later how many were written." > > > No way to know "what" is written? > And why no way to know "how many" times? > I'm not sure what that sentence means, and I've written code that uses co_lnotab. I think they are trying to explain the difficulties with abandoned approaches. Don't worry about that. Look at the code in the comment there to see how to interpret the bytes in co_lnotab. Here's the code in coverage.py that reads it: https://bitbucket.org/ned/coveragepy/src/a69ae93817be94e400df257e1b1e41cf37c9b146/coverage/parser.py?at=default#cl-377 if that helps. Just out of curiosity, what are you writing, it sounds interesting! :) --Ned. > > Regards > > -- Ned Batchelder, http://nedbatchelder.com
Back to top | Article view | comp.lang.python
csiph-web