Blog Posts from March 19, 2009 (page 1 of 1)
I really liked the ConsoleColorMgr class from my last ipydbg post so I took a few minutes to yank it out into its own seperate module. I also took the opportunity to make a few improvements.
First off, I added support for background colors as well as foreground colors. Furthermore, both colors default to “None” which ConsoleColorMgr takes to mean leave that color unchanged.
from System import Console as _Console class ConsoleColorMgr(object): def __init__(self, foreground = None, background = None): self.foreground = foreground self.background = background def __enter__(self): self._tempFG = _Console.ForegroundColor self._tempBG = _Console.BackgroundColor if self.foreground: _Console.ForegroundColor = self.foreground if self.background: _Console.BackgroundColor = self.background def __exit__(self, t, v, tr): _Console.ForegroundColor = self._tempFG _Console.BackgroundColor = self._tempBG
The other change I made was to build a set of default ConsoleColorMgr instances in the consolecolor module, one for each of the values in ConsoleColor.
import sys from System import ConsoleColor, Enum _curmodule = sys.modules[__name__] for n in Enum.GetNames(ConsoleColor): setattr(_curmodule, n, ConsoleColorMgr(Enum.Parse(ConsoleColor, n)))
Note that for this set of default ConsoleColorMgr instances, I’m only setting the foreground color. If you want to set the background color, you have to create your own ConsoleColorMgr instances. This allows me to write the following:
from __future__ import with_statement import consolecolor with consolecolor.Red: print "Open the pod bay doors, HAL" with consolecolor.ConsoleColorMgr(ConsoleColor.Black, ConsoleColor.Red): print "I'm sorry Dave, I'm afraid I can't do that."
Update: Christopher Bermingham
pointed out that my sample snippet at the end doesn’t work unless you
from future import with_statement to the top of your python file. I updated my code
snippet to include this. Thanks Christopher!
Now that I’ve added the current source code line to the console output, I wanted to start using color in order to make it clearer to understand the various pieces of data that gets output. Now, the various event handler messages get output in dark grey while the current line of source is in yellow. Here’s what it looks like on my machine (note, the top line with the green  is PowerShell and ipy2 is a PowerShell alias to ipy.exe v2.0.1)
Writing color to the windows console is a hassle because of the stateful API it uses. The problem is that I always want to return to the default color after I’ve written out a line of colored text. I wish there was an overload of Console.Write and WriteLine that took the foreground and background colors as arguments.
Of course, I could easily implement my own write and writeline methods that took color parameters. However, I was loath to do that as Python’s print statement is so convenient. So instead, I build a console color context manager. I got the idea from Luis Fallas’ XmlWriter context manager.
class ConsoleColorMgr(object): def __init__(self, color): self.color = color def __enter__(self): self.temp = Console.ForegroundColor Console.ForegroundColor = self.color def __exit__(self, t, v, tr): Console.ForegroundColor = self.temp CCDarkGray = ConsoleColorMgr(ConsoleColor.DarkGray) CCGray = ConsoleColorMgr(ConsoleColor.Gray) CCYellow = ConsoleColorMgr(ConsoleColor.Yellow) def OnCreateAppDomain(self, sender,e): with CCDarkGray: print "OnCreateAppDomain", e.AppDomain.Name e.AppDomain.Attach()
Python’s with statement is similar to C#’s using statement. However, unlike IDisposable object, Python context managers support both an enter and exit method. This means I don’t have to construct an object in order to get a context (in this case, the console colors) managed. So far, I’ve got three console color context managers defined – Grey, DarkGrey and Yellow. I’m thinking that ConsoleColorMgr is a candidate for my assorted module collection at some point.
Now that I can print in color, I wanted to modify my line printer to use color. Usually, the current sequence point corresponds to an entire line of python source. But as we see below, sometimes only part of a given line of source text is associated with a given sequence point.
The other issue I ran into is that there’s a always a sequence point at the very end of a function. Unlike the break at the start of the function I wrote about in my last post, this one I didn’t want to automatically step over. This is the last breakpoint for a given scope, so I should give the user one last chance to inspect the scope (once I add the ability to do that, at any rate) before we step out of it. However, I wanted a way of showing that we’re about to step out in the source code line view. I decided on writing a series of carets ^^^ to indicate that we’re at the end of a function.
As you can see in the dark grey line in the screenshot above, the current sequence point starts and ends at line 4 column 23. Column 23 is beyond the end of line 4, so that’s what I look for in order to draw the three carets. Here’s the final version of _print_source_line:
def _print_source_line(self, sp, lines): line = lines[sp.start_line-1] with CCGray: Console.Write("%d: " % sp.start_line) Console.Write(line.Substring(0, sp.start_col-1)) with CCYellow: if sp.start_col > len(line): Console.Write(" ^^^") else: Console.Write(line.Substring(sp.start_col-1, sp.end_col - sp.start_col)) Console.WriteLine(line.Substring(sp.end_col-1))
So colorizing the current line of source code turned out to be a little harder than I had expected. But hey, I got a start of a reusable module out of it. That’s pretty cool. Anyway, the latest bits are, as always, up on GitHub.
It’s been almost a week since my last ipydbg post. I’m not done, I just needed to catch my breath for a few days and get some other work done. Contrary to popular believe, my day job revolves around more than just ipydbg! 😄
Actually, I’ve made ten commit since my last post, but it’s been a mostly minor changes. For example, I was hacking around with breakpoints and restored a bunch of commented out code in BreakpointEnumerator. Since I was changing the original C# CorDebug wrapper source, I decided to add a few helper functions to return metadata for functions and classes as well as cleaning up some C# filenames. On the Python side, I added an active_appdomain field to IPyDebugProcess to go along with active_thread.
Today, I added what started as a fairly minor feature – showing the current line of source code at the start of the input loop. The initial code for this was cake, simply getting the sequence point for the current location and mapping that to a source file. In order to avoid hitting the file system over and over, I cache source files the first time they are accessed.
def _get_file(self,filename): filename = Path.GetFileName(filename) if not filename in self.source_files: self.source_files[filename] = File.ReadAllLines(filename) return self.source_files[filename] def _input(self): offset, sp = self._get_location(self.active_thread.ActiveFrame) lines = self._get_file(sp.doc.URL) print "%d:" % sp.start_line, lines[sp.start_line-1] #input loop ommited for clarity
However, when I did this, I discovered a slight issue. When you step into a Python function, the CLR debugger breaks at the very beginning of the function being stepped into. In C#, the function start is mapped to the opening curly brace of the function. IronPython, on the other hand, doesn’t map the start of the function to anything since there’s a bunch of infrastructure code at the start of every function that has no correlation to the python source. This means _get_location return a null sequence point when I first step into a function and thus I wouldn’t be able to show any source code.
I could make the argument that start of the function should be mapped to the colon that starts the function block. However, I’m not in a position to make changes to how the shipping version of IronPython emits debug symbols. So instead, I decided to insert an automatic step whenever I step into a function by modifying OnStepComplete:
def OnStepComplete(self, sender,e): offset, sp = self._get_location(e.Thread.ActiveFrame) print "OnStepComplete Reason:", e.StepReason, "Location:", sp if sp != None else "offset %d" % offset if e.StepReason == CorDebugStepReason.STEP_CALL: self._do_step(e.Thread, False) else: self._do_break_event(e)
I have this nagging feeling that a simple step won’t suffice and I’ll need to add logic to ensure that I’m only auto-stepping when the start of the function doesn’t have a matching sequence point. But I have tested this with a few different python scripts and it appears to work fine. If I need something more sophisticated, I can always add it later. BTW, notice I modified the signature of _do_step so that it takes the thread as an argument rather than picking it up as an IPyDebugProcess field.
As usual, latest ipydbg (including new compiled version of CorDebug.dll) is available at GitHub.