-
Notifications
You must be signed in to change notification settings - Fork 0
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
Document AnalysisError #127
Conversation
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.
What do you think?
Co-authored-by: Gabriele Barni <[email protected]>
Co-authored-by: Gabriele Barni <[email protected]>
Co-authored-by: Gabriele Barni <[email protected]>
I would kindly ask few more people who are the likely users of this feature to review the change. I add them in reviewers. Could you please help? |
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.
the sentence "is show below is shown below" is a leftover at line 233.
I do not understand why one should define a class, is you raise an exception is it not caught?
The lack of indentation does not allow me to understand if the "try: except is within the class or not. Maybe linking a usage example would be useful.
The indentation is not lacking here. This is a screenshot from the actual usage example: a Fermi notebook. Maybe using Ellipsis The idea of the dedicated class is to distinguish a properly handled exception in the notebook from the unexpected ones. |
Indeed, it was confusing, maybe you can link the example notebook if not done already.
|
Most example screenshots in this guide are made with the Fermi notebook, and it's referenced in the beginning |
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.
This looks good to me.
It's good practice to introduce designated Exception classes. This allows you to communicate errors more clearly than simply throwing a general excpetion (ie e.g. RuntimeError).
Thanks for reviewing! Does the text of the doc look comprehensive too, from a user point of view? |
Yes, the text is clear. It explains how you should handle errors. It is a good reminder to those who heard about this already. However, some users may not be familiar with the concept of classes in Python. Because you can write good code without this concept. But I would not care. You do not need to do it. The code will run fine even if you do not use classes. |
Should we merge? |
Ok, I think that'd be enough reviews. |
No description provided.