0.0.24 - #24
Merged
Merged
Conversation
added 14 commits
April 20, 2026 19:03
detection and resolution via custom getters
truncation logic and edge cases for bytes, ellipsis, and mixed truncation scenarios.
test_superrepr_for_lambda_without_source
This file contains hidden or 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
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.
A small but useful update. It mainly focuses on clarifying various edge cases for features added previously.
python3 -c "from printo import superrepr; print(superrepr(lambda value, extra: False))"now always correctly outputs either theλsymbol or the full lambda function code.Ellipsis, as otherwise this would only add extra dots.repr()function, where quotes and escape characters are added to it. The length of the ellipsis and quotes is not taken into account when truncating the string.@repreddecorator.