You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in bdb, when a new function is entered, bdb checks if it's possible that there's a breakpoint in that function and only enable events in that function if there is. It's a good strategy but the existing check is too loose. It equivalently check if there is a breakpoint in the file that function is defined in.
We have much better tools to determine whether the function has a breakpoint in it now. Without enabling unnecessary events in those functions, pdb would be much faster.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Feature or enhancement
Proposal:
Currently in
bdb
, when a new function is entered,bdb
checks if it's possible that there's a breakpoint in that function and only enable events in that function if there is. It's a good strategy but the existing check is too loose. It equivalently check if there is a breakpoint in the file that function is defined in.We have much better tools to determine whether the function has a breakpoint in it now. Without enabling unnecessary events in those functions, pdb would be much faster.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: