PR: Remove set_debug_state and do_where calls
#411
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
impact27
force-pushed
the
remove_set_debug_state
branch
3 times, most recently
from
76a5a81
to
800db7d
Compare
impact27
force-pushed
the
remove_set_debug_state
branch
from
800db7d
to
8228197
Compare
ccordoba12
changed the title
set_debug_state calls
impact27
changed the title
set_debug_state callsset_debug_state and do_where calls
ccordoba12
approved these changes
Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
set_debug_stateis a call that doesn't really add value as the debugging information is contained in the debugging prompts.do_wherecan simply be added to the stategoes with: spyder-ide/spyder#19350