search

ternaris / marv

THIS REPOSITORY HAS BEEN MERGE INTO
https://github.com/ternaris/marv-robotics
GNU Affero General Public License v3.0
3 stars 4 forks source link

Best practice for debugging custom nodes #20

Closed beetleskin closed 6 years ago

beetleskin commented 6 years ago

While development, I encounter cryptic errors a lot. Is there a best practice to debug custom nodes, started from cli, with the python debugger and step through it? Using ye old debug-prints is very cumbersome and time-consuming.

NikolausDemmel commented 6 years ago

Yes, AFAIK ipdb is the way to go. You can set a break point with

import pdb; pdb.set_trace()

And isn't there a marv-ipdb executable as well that can be used as a drop-in replacement for marv?

beetleskin commented 6 years ago

That's what I'm was looking for, thanks!