-
Notifications
You must be signed in to change notification settings - Fork 20
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
Many methods default to pretty=True
, and use print()
#236
Comments
Hi @mgeplf, At the beginning, the goal was more to use forge in the context of a Jupyter notebook. Hence the prints across the methods you highlighted. But we are happy to see it now used also as a lib. I know some of the team member found this pecurliar too.
Happy to discuss this with you. Currently, a client can always set 'pretty=False' or a different 'output' to get a result rather than printing. Are you suggesting to have it the other way around, ie. default to returning ? Or do you have other suggestion ? @kplatis , @annakristinkaufmann , @eugeniashurko, @nabil-al : what are you thoughts on this? |
Yup, fair enough, I'm just hoping we can revisit that decision; if we can't, I understand. I wonder if we can rely more on jupyter to present the data. For instance, one can do:
Having the user in the habit of printhing things when they want allows for more options, imo.
Yes, I think that would be the minimal change. I also think that:
|
Any updates on this? Does it seem like a good direction? |
Hi. @mgeplf ,
Yes. Thanks for the input. I'll pick up this item next week. |
I believe that nexus-forge is mainly to be used as a library (correct me if I'm wrong), and thus I find the decision to
print()
things pecurliar. Normally, I would expect a library to remain as quiet as possible, possibly using thelogging
orwarnings
packages to give feedback in error conditions.In this case, however, the following API calls appear to print by default:
Could we reopen this design decision?
The text was updated successfully, but these errors were encountered: