The only feedback I’ve gotten so far about the IronPython Profiler is that it would be nice not to have to specify a command-line option to use it. Imagine that you’ve got a REPL open and are in the middle of some interactive development – something at which I think Python excels. You’ve spent a fair amount of time setting up data and code, but now there’s something that’s running slowly that you’d like to analyze.
Profiler Part II: Poor Man’s Code Coverage
- 11th April 2009
- 2008, 2009, 3.0, action, ads, anonymous, app, application, archive, art, atom, Blog, build, cd, change, cloud, code, color, community, compile, control, Cookie, course, css, data, development, ea, EFI, email, event, events, free, fun, gdc, hd, ical, im, ion, javascript, language, languages, love, ls, mail, march, media, Meta, microsoft, Microsoft Rules, new, news, NIN, open, order, OS, play, port, post, pro, project, Q1, record, release, rip, screen, script, search, server, source, tag, tags, tasks, theme, themes, time, tor, trends, ui, uk, unity, update, used, value
- ads, application, atom, cloud, compile, control, data, EFI, events, fun, gdc, ical, ion