RetroSearch Browse

Fri Oct 6 14:53:28 EDT 2017 · https://mail.python.org/pipermail/python-dev/2017-October/149794.html

apologies - I didn't "reply all" to this.
For the record:

I made an argument (in reply) about interactive tinkering, and setting
"condition",
and Guido replied essentially that "if condition: breakpoint()" is just as
good for tinkering... a condition parameter to debuggers is not useful, and
not as explicit.

Yes - agreed (and the `gist` which I tinkered w/ one day - I've now
discarded ;-).

Thanks, Guido!
- Yarko

On Wed, Oct 4, 2017 at 9:12 PM, Guido van Rossum <guido at python.org> wrote:

> Yarko, there's one thing I don't understand. Maybe you can enlighten me.
> Why would you prefer
>
> breakpoint(x >= 1000)
>
> over
>
> if x >= 1000: breakpoint()
>
> ?
>
> The latter seems unambiguous and requires thinking all around. Is there
> something in iPython that makes this impractical?
>
> --
> --Guido van Rossum (python.org/~guido)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171006/8527c5db/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-October/149794.html below:

[Python-Dev] PEP 553