Cyberbrain: Python debugging, redefined.

Cyberbrain¹(电子脑) aims to free programmers from debugging. It lets you:

• Backtrace variable changes.

• See every state of program execution, including variables' values

• Debug loops with confidence.

Never spend hours stepping through a program, let Cyberbrain tell you what happened.

Read more about existing features, and roadmaps for features to come.

I gave a talk at PyCascades 2021 about Cyberbrain, watch it here.

Install

Cyberbrain consists of a Python library and various editor/IDE integrations. Currently it supports VS Code and Gitpod. See our plan on expanding the support.

To install Cyberbrain:

pip install cyberbrain
code --install-extension laike9m.cyberbrain

You can also install from PyPI , VS Code marketplace or Open VSX .

Or, you can try Cyberbrain online:

How to Use

Suppose you want to trace a function foo, just decorate it with @trace:

from cyberbrain import trace

# As of now, you can only have one @trace decorator in the whole program.
# We may change this in version 2.0, see https://github.com/laike9m/Cyberbrain/discussions/73

@trace  # Disable tracing with `@trace(disabled=True)`
def foo():
    ...

Cyberbrain keeps your workflow unchanged. You run a program (from vscode or command line, both work), and a new panel will be opened to visualize how your program executed.

The following gif demonstrates the workflow (click to view the full size image):

Read our documentation to learn more about Cyberbrain's features and limitations.

❗Note on use❗

• Cyberbrain may conflict with other debuggers. If you set breakpoints and use VSC's debugger, Cyberbrain may not function normally. Generally speaking, prefer "Run Without Debugging" (like shown in the gif).
• If you have multiple VS Code window opened, the trace graph will always be created in the first one. #72 is tracking this issue.
• When having multiple decorators, you should put @trace as the innermost one.

  @app.route("/")
  @trace
  def hello_world():
      x = [1, 2, 3]
      return "Hello, World!"

Roadmaps

Updated 2020.11

Cyberbrain is new and under active development, bugs are expected. If you met any, please create an issue. At this point, you should NOT use Cyberbrain in production. We'll release 1.0 when it's ready for production.

Major features planned for future versions are listed below. It may change over time.

Visit the project's kanban to learn more about the current development schedule.

How does it compare to other tools?

Community

• 💬 GitHub Discussions (for general discussions)
• 🤖 Discord (for more instant discussions. I'm happy to chat any time!)
• 🐦 Twitter @PyCyberbrain (for announcements)

Interested in Contributing?

See the development guide. This project follows the all-contributors specification. Contributions of ANY kind welcome!

Thanks goes to these wonderful contributors ✨

Alex Hall 🤔	Frost Ming 🐛 📖	Funloading 💻	Ikko Ashimine 💻	Kaustubh Gupta 📝	Ram Rachum 🤔	Siyuan Xu 🐛	Victor Sun 💻 🤔	dingge2016 💵 💻	foo bar 💵
inkuang 🐛	laixintao 📖	yihong 💵 🤔	林玮 (Jade Lin) 🐛 🤔

Support

Cyberbrain is a huge and complicated project that will last for years, but once finished, it will reshape how people think and do debugging. Your support can help sustain it. Let's make it the best Python debugging tool 🤟!

❤️ Sponsor on GitHub

¹: The name of this project originates from Ghost in the Shell, quote:

Cyberization is the process whereby a normal brain is physically integrated with electronic components to produce an augmented organ referred to as a cyberbrain.