Hi Udo, My debugging strategy is just putting in a lot of "print" statements and then take them out before committing.May be old fashioned, but it kind of works for me.
More systematic debugging I do by writing test coverage for functions. If errors are reported having a test case in the suite that triggers on error is the best way to address it. Regards, Jaap On Tue, Feb 17, 2015 at 7:34 PM, Udo Weik <weikeng...@aol.com> wrote: > Hello, > > I'm looking for infos how the source code/plugins can be debugged > (Windows 7 Professional, 64 Bit SP1). Would prefer the PyCharm > Community Edition from JetBRAINS as IDE: > https://www.jetbrains.com/pycharm/ > http://www.jetbrains.com/ > > > Many thanks and greetings > Udo > > _______________________________________________ > Mailing list: https://launchpad.net/~zim-wiki > Post to : email@example.com > Unsubscribe : https://launchpad.net/~zim-wiki > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~zim-wiki Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~zim-wiki More help : https://help.launchpad.net/ListHelp