Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Sun, 22 Feb 2015 13:14:24 -0600
From: Tim Chase <python.list@tim.thechases.com>
To: "Jacob Kruger" <jacob@blindza.co.za>, <python-list@python.org>
Subject: Re: Accessible tools
In-Reply-To: <D3C58D9CD8CA4079AE0FEDE2097F0689@JakesPC>
References: <479CFB67BB2640C09ADB16742A547172@JakesPC> <00DB5382-A26A-4157-898E-854C6C14CDF0@gmail.com> <20150221122918.7e4e39eb@bigbox.christie.dr> <D3C58D9CD8CA4079AE0FEDE2097F0689@JakesPC>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.19022.1424632963.18130.python-list@python.org>
Lines: 48
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:86147

On 2015-02-22 20:29, Jacob Kruger wrote:
> jaws, doesn't always cooperate perfectly with command line/console
> interface

I've heard that on multiple occasions.  Since I mostly work with
Linux, the only terminal-with-screen-reader hints I've heard involve
using TeraTerm as the SSH client with NVDA on Windows.  Sorry I can't
be of much more assistance there, since I haven't really used Windows
for years.

> this page seems to offer enough detail relating to PDB, to start
> off with anyway: https://docs.python.org/3/library/pdb.html

My generally process is as follows:

1) add the following line some place before where I want to debug:

   import pdb; pdb.set_trace()

2) run my program

3) when it hits that line of code, it drops you to the debugging
prompt

4) poke around, using "print" followed by the thing(s) I want to
inspect such as

  print dir(something)
  print my_var.some_field

5) step to the next line of code with "n" or step into a
function/method call with "s" or exit/return from the current
function/method with "r".  I'll also use "l" (ell) to list some
context around the current line so I can tell where I am in the
source code.  This is particularly helpful as I can use the
corresponding line-number(s) to jump to the same line in my editor if
I spot the offending line of code, then edit it.

very rarely, I'll actually set additional breakpoints (optionally
making them conditional) but I *always* have to look up the syntax
for that.

Hopefully that gets you at least to the point where debugging isn't
some laborious task.  Best wishes,

-tkc