Breaking in StdLib while not stepping into

未关闭

#854 创建于 2022年2月4日 6 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

还没有人认领这个 Issue。

评估

难度: 5/5
预计耗时: 一周以上
新手友好度: 30/100

Issue 类型: 缺陷
描述清晰度: 需要澄清
活跃度: 停滞
技术栈: jupyter, jupyter-notebook, python
领域: backend, devtools

调研方向

首先阅读 ipykernel PR #812 和 #839、issue #832，以及链接的 JupyterLab PR #11566，以了解已更改的单步执行行为。该 issue 未指定源文件或测试；完成意味着定义并验证一种在 userland 文件和标准库文件中中断的方法，同时不会意外地单步执行这些文件。

由索引模型根据 Issue 内容生成。

描述

JupyterLab 3.3.0a3 has a kernel sources panel which displays the loaded py files loaded (so the core python libraries, and userland libraries). This aims to offer the user the ability to add breakpoints and debug to see what happens in those userland libraries.

https://github.com/ipython/ipykernel/pull/812 has added the needed option to be able break into those stdlib files, while https://github.com/ipython/ipykernel/pull/839 has removed it. The removal is due to https://github.com/ipython/ipykernel/issues/832 where the step was going to the line in the call stack. Interesting to note, today the side effect describe in https://github.com/jupyterlab/jupyterlab/pull/11566#issuecomment-983668657 (breaking in selector.py) has disappeared.

Thinking a bit more, the behavior is expected. When we say to debugpy to break into all files, we also say to step into all files, meaning that the taken step goes to the next in the call stack, including the StdLib files.

@JohanMabille You say on https://github.com/ipython/ipykernel/issues/832#issuecomment-1010414146 that you would think to a solution ...changing the step over behavior, or filter stop events. Is there anything we can do in the short therm?

主要语言: Python
星标: 734
派生: 411
平均合并: 1 天 2 小时
30 天内合并 PR: 9