A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-July/007680.html below:

[Python-Dev] Reordering opcodes (PEP 203 Augmented Assignment)

[Python-Dev] Reordering opcodes (PEP 203 Augmented Assignment) [Python-Dev] Reordering opcodes (PEP 203 Augmented Assignment)Mark Hammond mhammond@skippinet.com.au
Mon, 31 Jul 2000 11:45:01 +1000
> Can someone summarise what the issues are with SET_LINENO?
> I had the impression that they're not needed for finding the
> line numbers in tracebacks. So what would we lose if they
> disappeared?

The debugger (and quite possibly the profiler - I havent checked!)

As Tim said only a few hours ago:

---
Your next job <wink> is to think about how, e.g., you can set a breakpoint
on a specific line of code in the debugger.  Take a quick peek at the
implementation of SET_LINENO in ceval.c, and you'll see that's where the
trace hook is implemented.  No SET_LINENO, no trace callback.  That's what
Vladimir has been trying to solve:  the trick is arranging to pay something
at runtime for it only when you're actually using it.

debuggers-always-need-dirty-tricks-ly y'rs  - tim
---

Mark.




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4