Refactor __str__ methods for readability and consistency #43
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.
Refactor: modernize and unify
__str__methods across transaction classesThis PR updates the
__str__implementations for several transaction-related classes to improve readability, consistency, and maintainability while preserving exact output semantics.Summary of changes
%formatting with f-strings for clarity and modern Python style.bh2u) exactly as before where originally present.sequeence).Affected components
CTxInCTxOutProRegTxProUpRegTxProUpRevTxCbTxAssetLockTxAssetUnlockTxWhy this change
The original
__str__implementations were inconsistent in style and used legacy formatting.This cleanup makes the codebase more uniform and maintainable while ensuring output remains fully backward-compatible.
Compatibility
✔ No behavior changes
✔ No serialization logic changes
✔ Output format preserved
✔ Safe for all downstream consumers (GUI/logs/tests)