fix: Printed results not visible in debugger & notebooks #296
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
simicd
changed the title
andygrove
approved these changes
Mar 22, 2023
|
You're welcome, thanks for the review @andygrove! |
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.
Which issue does this PR close?
Closes #291
Rationale for this change
Previously printing results (e.g.
.show()method or.explain()) used Rust'sprintln!macro. The results would not be visible in VS Code's debug console or in notebooks. Example:What changes are included in this PR?
Use Python's builtin print function to resolve the issue and allow displaying results directly in the debugger & notebooks:
Are there any user-facing changes?
.show()and.explain()newly display results