Title: Implement PEP 553 - built-in breakpoint()
Type: enhancement Stage: resolved
Components: Interpreter Core Versions: Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: barry Nosy List: Ethan Smith, alkuzad, barry, r.david.murray
Priority: normal Keywords:

Created on 2017-09-05 20:44 by barry, last changed 2017-10-05 16:11 by barry. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 3355 merged barry, 2017-09-05 20:44
Messages (4)
msg301372 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2017-09-05 20:44
Placeholder issue for discussion of the design of the implementation of PEP 553.
msg302109 - (view) Author: Dawid Gosławski (alkuzad) Date: 2017-09-13 19:54
Will that be backported also to Python2.7 ? I personally do not see a reason to teach old dog new tricks but it seems appropriate in such core things. New users could transition easier, otherwise this would be next py2<->py3 difference to explain every time someone uses new code.
msg302110 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2017-09-13 20:00
It is a new feature, so no it would not be backported.
msg303573 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2017-10-03 00:22
PEP is accepted.  PR needs review.
Date User Action Args
2017-10-05 16:11:54barrysetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2017-10-03 05:50:21serhiy.storchakasettitle: Implement PEP 553 - built-in debug() -> Implement PEP 553 - built-in breakpoint()
2017-10-03 00:22:53barrysetmessages: + msg303573
stage: patch review
2017-09-13 20:00:14r.david.murraysettype: enhancement

messages: + msg302110
nosy: + r.david.murray
2017-09-13 19:54:43alkuzadsetnosy: + alkuzad
messages: + msg302109
2017-09-06 08:11:29Ethan Smithsetnosy: + Ethan Smith
2017-09-05 20:44:52barrysetpull_requests: + pull_request3370
2017-09-05 20:44:20barrycreate