Changes by Petr Viktorin encu...@gmail.com:
--
nosy: +encukou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22444
___
___
Python-bugs-list mailing
Petr Viktorin added the comment:
I tried my hand at writing a patch. I hope it is helpful.
The message of the 2001 commit that introduces this says that there's no
platform-independent way to write a test case for this. I assume with
@support.requires_IEEE_754 that is no longer true (at least
Petr Viktorin added the comment:
Note: I signed the contributor agreement form recently, I should have a * soon.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22198
New submission from Petr Viktorin encu...@gmail.com:
Consider this program:
import pdb
pdb.set_trace()
print (At line 5)
print (At line 6)
print (At line 7)
print (At line 8)
print (At line 9)
When set_trace starts the debugger, I set a breakpoint at line 8. When I
do that, the continue
Petr Viktorin encu...@gmail.com added the comment:
It doesn't matter whether the breakpoint is set from within a function
or not, but only the module-level frame is affected.
import pdb
def test():
print (At line 4)
print (At line 5)
print (At line 6)
print (At line 7
New submission from Petr Viktorin encu...@gmail.com:
In the yield statement documentation
(http://docs.python.org/3.0/reference/simple_stmts.html#the-yield-statement),
the old way of calling generators is used:
The body of the generator function is executed by calling the
generator’s next
901 - 906 of 906 matches
Mail list logo