Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement __repr__ properly in dictionary classes #54

Closed
popescu-v opened this issue Jul 4, 2023 · 2 comments
Closed

Implement __repr__ properly in dictionary classes #54

popescu-v opened this issue Jul 4, 2023 · 2 comments
Assignees
@tramora
Labels
Status/Obsolete The issue is not relevant anymore or it has been addressed by another one Type/DevChore Repository maintainance, CI/CD or non user-facing refactorings

Comments

@popescu-v
Copy link
Collaborator

Currently the __repr__ and __str__ are equal. __repr__ however should be a succint unambiguous representation of the object.

We should discuss first what should be this representation.
@popescu-v popescu-v added Status/Draft The issue is still not well defined Type/DevChore Repository maintainance, CI/CD or non user-facing refactorings labels Jul 4, 2023
@popescu-v
Copy link
Collaborator Author

__repr__ needs indeed to be unambiguous, but it doesn't need to be succinct.

On the other hand, __str__ needs to be readable; it doesn't need to be unambiguous. But it'd rather be succinct, for better readability.

@folmos-at-orange folmos-at-orange added the Priority/1-Medium To do after P0 label Mar 12, 2024
@popescu-v
Copy link
Collaborator Author

Superseded by #229

@popescu-v popescu-v closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
@popescu-v popescu-v added Status/Obsolete The issue is not relevant anymore or it has been addressed by another one and removed Status/Draft The issue is still not well defined labels Oct 28, 2024
@folmos-at-orange folmos-at-orange removed the Priority/1-Medium To do after P0 label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tramora tramora

Labels
Status/Obsolete The issue is not relevant anymore or it has been addressed by another one Type/DevChore Repository maintainance, CI/CD or non user-facing refactorings
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tramora @folmos-at-orange @popescu-v