Hi Dennis,
From the look of the error message, there might have been some subtle changes in argparse between 2.7 and 3.5; however, I can’t say I know what those changes are. The documentation will probably describe the changes.
However, before you start sinking too much time into Bugjar, some warnings:
* Even on Python 2, it’s a bit unstable. It needs a lot of work. The instability is mostly tied to the robustness of the communications channel. There’s a lot of work that needs to be done on the internals before it’s really a viable debugger.
* I’m planning to do a big rework of the GUI at some point in the near future. I haven’t worked on Bugjar for almost 3 years, mostly because I hit the limits of what I could do with Tkinter, and got distracted working on a replacement (called Toga).
If you’re especially enthused to work on Bugjar specifically, I certainly don’t want to stop you. But if you’re just looking for a project to contribute to, I can suggest some better options - essentially on the precursor work that will (eventually) make Bugjar a lot easier to write.
Yours,
Russ Magee %-)