On Mon, Apr 30, 2012 at 12:31 PM, Xavier de Gaye wrote:
Issue http://bugs.python.org/issue13183 raises the point that the step
command of pdb is broken. This issue is 6 months old. A patch and test
case have been proposed.
Other pdb commands are also broken for the same reason (no trace
Issue http://bugs.python.org/issue13183 raises the point that the step
command of pdb is broken. This issue is 6 months old. A patch and test
case have been proposed. The 'Lifecycle of a Patch' at
http://docs.python.org/devguide/patch.html says
quote
If your patch has not received any notice from
IT would be good if the author of one of the pdb add-ons such as (I
believe) pdb2 could comment on this bug.
On Mon, Apr 30, 2012 at 3:31 AM, Xavier de Gaye xdeg...@gmail.com wrote:
Issue http://bugs.python.org/issue13183 raises the point that the step
command of pdb is broken. This issue is 6
On Apr 30, 2012, at 08:42 AM, Guido van Rossum wrote:
IT would be good if the author of one of the pdb add-ons such as (I
believe) pdb2 could comment on this bug.
Maybe we should take this opportunity (Python 3.3) to consider adopting one of
the pdb add-ons or borging the best of their bits into
On Mon, Apr 30, 2012 at 9:09 AM, Barry Warsaw ba...@python.org wrote:
On Apr 30, 2012, at 08:42 AM, Guido van Rossum wrote:
IT would be good if the author of one of the pdb add-ons such as (I
believe) pdb2 could comment on this bug.
Maybe we should take this opportunity (Python 3.3) to
On Mon, Apr 30, 2012 at 12:09:02PM -0400, Barry Warsaw wrote:
Maybe we should take this opportunity (Python 3.3) to consider adopting one of
the pdb add-ons or borging the best of their bits into the stdlib?
Irrespective of this - Issue13183 seems to be an easy to verify bug in
3.2 and 3.3. I
Senthil, if you can shepherd this patch to completion that would be great!
On Mon, Apr 30, 2012 at 9:57 AM, Senthil Kumaran sent...@uthcode.com wrote:
On Mon, Apr 30, 2012 at 12:09:02PM -0400, Barry Warsaw wrote:
Maybe we should take this opportunity (Python 3.3) to consider adopting one
of
On Mon, Apr 30, 2012 at 6:57 PM, Senthil Kumaran wrote:
Irrespective of this - Issue13183 seems to be an easy to verify bug in
3.2 and 3.3. I think, it would most visible if you were to use a full
screen debugger and you will notice that the return call indicator has
jumped to the next
On 30.04.2012 18:09, Barry Warsaw wrote:
On Apr 30, 2012, at 08:42 AM, Guido van Rossum wrote:
IT would be good if the author of one of the pdb add-ons such as (I
believe) pdb2 could comment on this bug.
Maybe we should take this opportunity (Python 3.3) to consider adopting one of
the pdb
