In article ,
Piotr Dobrogost wrote:
> On Thursday, April 11, 2013 5:12:53 PM UTC+2, donald...@gmail.com wrote:
> > I just submitted a bug report on the pdb issue.
> It would be nice of you to share the link to this issue.
http://bugs.python.org/issue17697
--
Ned Deily,
n...@acm.org
--
ht
On Thursday, April 11, 2013 5:12:53 PM UTC+2, donald...@gmail.com wrote:
>
> I just submitted a bug report on the pdb issue.
It would be nice of you to share the link to this issue.
--
http://mail.python.org/mailman/listinfo/python-list
On Thu, Apr 11, 2013 at 12:42 PM, Robert Kern wrote:
> Use `where` to see the problem:
Ah. Then I can verify that the problem occurs in Windows as well:
C:\Users\ikelly\Desktop>c:\python33\python python_bug.py
first call
--Return--
> c:\users\ikelly\desktop\python_bug.py(7)foo()->None
-> pdb.se
On 2013-04-11 23:11, Ian Kelly wrote:
On Thu, Apr 11, 2013 at 8:56 AM, wrote:
#! /usr/bin/env python3
import pdb
def foo(message):
print(message)
pdb.set_trace()
foo('first call')
foo('second call')
Stick this in an file with execute permission and run it. At the first
brea
On Thu, Apr 11, 2013 at 8:56 AM, wrote:
> #! /usr/bin/env python3
> import pdb
> def foo(message):
> print(message)
> pdb.set_trace()
> foo('first call')
> foo('second call')
>
> Stick this in an file with execute permission and run it. At the first
> breakpoint, the backtrace wi
On Tuesday, April 9, 2013 6:17:28 PM UTC-4, Ned Deily wrote:
> In article ,
>
> donallen wrote:
>
>
>
> > I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit
>
> > Arch Linux system) and am attempting to use pdb to debug it. I am getting
>
> > incorrect stack traces
> > Suggestions?
>
>
>
> Post the 10-line program here, so others can verify whether it is a bug.
#! /usr/bin/env python3
import pdb
def foo(message):
print(message)
pdb.set_trace()
foo('first call')
foo('second call')
Stick this in an file with execute permission and run it.
In article ,
Gregory Ewing wrote:
> Ned Deily wrote:
> > There is a meta tracker for problems with the Python
> > issuer tracker itself:
> > http://psf.upfronthosting.co.za/roundup/meta/
> > but you do have to register for that tracker (a separate registration).
> You mean there's no meta-meta
Ned Deily wrote:
There is a meta tracker for problems with the Python
issuer tracker itself:
http://psf.upfronthosting.co.za/roundup/meta/
but you do have to register for that tracker (a separate registration).
You mean there's no meta-meta-tracker for reporting
problems registering with t
In article ,
donaldcal...@gmail.com wrote:
> I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit
> Arch Linux system) and am attempting to use pdb to debug it. I am getting
> incorrect stack traces. I've made up a little 10-line program that
> illustrates the problem an
In
donaldcal...@gmail.com writes:
> I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit=
> Arch Linux system) and am attempting to use pdb to debug it. I am getting =
> incorrect stack traces. I've made up a little 10-line program that illustra=
> tes the problem and I a
On 9 April 2013 16:25, wrote:
> I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit
> Arch Linux system) and am attempting to use pdb to debug it. I am getting
> incorrect stack traces. I've made up a little 10-line program that
> illustrates the problem and I attempted
I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit
Arch Linux system) and am attempting to use pdb to debug it. I am getting
incorrect stack traces. I've made up a little 10-line program that illustrates
the problem and I attempted to register on the bug-tracker site,
u
13 matches
Mail list logo
