Éric Araujo <mer...@netwok.org> added the comment: [Terry] > Binary search with print is done manually. If error not obvious from quick > read, in a 20 line > function, add print around line 10. If ok there, look down and add print > later in function. [...] Okay, so it’s what I thought only I didn’t had the name :)
> More time: read outline, good start. Thanks! I’ll publish a repo when I start writing. [Ezio] > Hadn’t though about coverage. Will mention it and add a link > to the devguide part that talks about it. > Is devguide/coverage.html#using-coverage-py generic enough? I had a quick look and it looks good. > We don't have to duplicate the coverage documentation though, mentioning the > tool and what it > does, provide a couple of simple example and a link to the coverage doc > should be enough. Yep, I was thinking about mentioning, nothing more. >> - running Python in gdb > This is somewhat orthogonal, but the devguide/gdb page doesn't say how to > start running Python > in gdb (it might be obvious to people used to use gdb, but it should still be > mentioned). If the devguide is updated, I will be content with just one line containing one link in my howto. Currently we have this wiki page: http://wiki.python.org/moin/DebuggingWithGdb I also remember a ubuntu wiki page with more useful info but can’t find the bookmark. FTR, I will use these resources: https://pythonconquerstheuniverse.wordpress.com/2009/09/10/debugging-in-python/ and http://www.jeetworks.org/node/99 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12913> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
