New submission from anatoly techtonik email@example.com:
Documentation for pdb says: "The debugger is extensible — it is actually defined as the class Pdb. This is currently undocumented but easily understood by reading the source."
There should a link to the source.
assignee: docs@python components: Documentation, Library (Lib) messages: 162074 nosy: docs@python, techtonik priority: normal severity: normal status: open title: pdb: Link to source
Éric Araujo firstname.lastname@example.org added the comment:
Sounds good to me. Raymond, do you concur?
nosy: +eric.araujo, rhettinger title: pdb: Link to source -> pdb doc: Add link to source versions: +Python 2.7, Python 3.2, Python 3.3
Senthil Kumaran email@example.com added the comment:
Adding link to pdb source may be not be suitable. Readers may require to understand the states which pdb goes through. Docs here are better, IMO. -1 vote from me.
anatoly techtonik firstname.lastname@example.org added the comment:
I agree that reading the source doesn't make it clear how to extend or use PDB, so I've changed the title. High level overview is required.
I think an example would really help there. For instance a simple execution scroller -
python -m trace --trace <filename.py>, but with PDB and
play/pause buttons controlled from external script.
title: pdb doc: Add link to source -> pdb doc: Explain how to extend debugger instead of sending readers to the source
anatoly techtonik added the comment:
A minimal example of debugger is needed, with the explanation how frame.f_trace is used by debuggers.
versions: +Python 3.4, Python 3.5
Change by Irit Katriel email@example.com:
type: -> enhancement versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5