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.
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.
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
Add feature to print result parts to console #56
base: main
Are you sure you want to change the base?
Add feature to print result parts to console #56
Changes from 1 commit
27b12b8
bb86441
304996e
466c349
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be beneficial to also have access to the value and the uncertainties as numeric values, not only as strings? For example,
In this case, we should make very clear in the docs that the object returned by
wiz.res()
is non-modifiable, e.g. you cannot setres.value = 42
afterwards and expect the underlying value to change. It is read-only.But maybe that is overkill and we should leave it at strings. One could also argue that the user already knows the numerical value upfront, so they could instead just assign it the a local variable before passing it to
wiz.res()
and would be good to go... This would also avoid confusion about the modifiability ob the object returned bywiz.res()
since when you only get back strings, you probably don't expect that this would modify the underlying valueres.value = "42.0"
. In that case, maybe we can even drop the "str" part of the method names? Since the datatype is clear by the method signature-> str
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree :-)