ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Python Debugger

by wvlia5 ST3

Graphical Debugger for Sublime Text

Details

Installs

  • Total 6K
  • Win 3K
  • OS X 1K
  • Linux 2K
Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11
Windows 14 2 0 19 29 16 24 17 22 21 14 26 18 16 26 17 25 20 30 27 29 11 15 30 35 28 26 22 14 14 20 26 27 22 22 14 11 33 22 20 24 12 11 12 13 31
OS X 8 0 0 9 8 9 10 8 22 5 7 8 10 11 12 3 7 6 11 9 8 3 8 10 12 10 8 13 9 5 9 9 9 4 12 7 7 12 12 16 9 8 4 4 6 13
Linux 7 3 0 11 8 17 5 8 7 12 17 8 13 12 9 9 11 8 7 12 6 13 13 13 8 9 10 14 2 8 14 4 14 17 11 16 7 12 12 13 7 11 10 7 10 10

Readme

Source
raw.​githubusercontent.​com

SublimeDebugger

This is a graphical debugger for Sublime Text 3.

screenshot

Hire Me

The developer of this project needs a job. I can relocate anywhere in the world or work remotely. I have a degree in Mechanical Engineering. wvlia5@live.com.ar

Features

  • Setting breakpoints, using either keyboard shortcuts or the console.
  • Local and Global Variables Inspector
  • Expression Watcher
  • Breakpoints Editor
  • Step, Continue, Next, Outer/Inner frame through the console

Languages Supported

  • Python 2
  • Python 3

How to add support to your favourite Language

You've got to write a backend for the debugger. They are located in the backends folder. Your backend should implement a class with the following members (Which will be called by the frontend):

  • set_break(filename, line, bpinfo)

Is called by the frontend to set a breakpoint. bppinfo is a dict containing info about the breakpoint (backend dependant).

  • clear_break(filename, line)

Is called by the frontend to clear a breakpoint.

  • toggle_break(filename, line)

Is called by the frontend to toggle a breakpoint.

  • tryeval(expr)

Is called by the frontend to evaluate an expression. It is needed to fill the Expression Watcher. Should return the result of the evaluated expression in the current context.

  • runscript(filename)

Is called by the frontend to start debugging a program.

  • breakpoints

A dict of breakpoints. The structure of the dict is the following:

{
    filename1:
    {
        line1: bpinfo1,
        line2: bpinfo2,
        line3: bpinfo3,
        etc..
    },
    filename2:
    etc..
 }

where each bpinfo is a dict with backend dependant content.

  • parent

An member that will be set by the frontend, it will have the methods mentioned next.

Additionally, the following methods of the frontend should be called by your backend when relevant (accessed through the parent member of your backend):

  • get_cmd(line, locals, globals, filename)

Request a command from the user.

  • set_break(filename, line, bpinfo)

Set a breakpoint in the Sublime GUI

  • clear_break(filename,line)

Clear a breakpoint of the Sublime GUI

  • toggle_break(filename,line)

Toggle a breakpoint in the Sublime GUI

  • show_help(help_str)

Show the help message help_str in Sublime

  • show_exception(message)

Show an exception message in Sublime

Then import the backend from mydebugger.py. Add your language to Main.sublime-menu and to languageCommand in mydebugger.py

The Python3 backend (dbPython3.py) is the simpler one, take a look at that for guidance. Also, contact me if you really mean to implement one, I'll help you so we can include it here afterwards. wvlia5@live.com.ar

TODO

  • ST2 support?
  • better exception handling (I think it can't be made better since it is managed by bdb)
  • toggle hide special members
  • configuring breakpoints from Breakpoints Watcher?
  • multifile support
  • test on windows
  • context key bindings with filename?