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
Consider using specific exceptions rather than generic Exception
#15
Comments
Well okay, fair enough --- I can see that one could use the various
|
Yes, one major problem with using
When I see the error, I search for "NAME" in the code and don't find it. I am used to seeing python errors that use the variable names with the same case that they have in the code. |
Ah, okay --- no problem. Catching things like I'm not keen to update some of the other formatting type aspects though --- there's a broader, multi-language style that I try to maintain across jigsaw in general, and some of these quirks are examples of that. For issues of maintainability, as well as my own sanity, many of the comment strings, data structure layouts, etc, etc are as common as possible across jigsaw's underlying C++ implementation as well as the various other language bindings. |
Okay, do as you see fit. I only will reiterate that |
I swapped from |
I appreciate that. |
Updated to |
I don't find the exceptions raised by
jigsawpy
to be very intuitive, and I think that might be true for most python users.As an example:
jigsaw-python/jigsawpy/savemsh.py
Line 613 in f875719
I would expect something like:
As I understand it, the generic
Exception
class is only intended as a base class for exceptions and shouldn't be used directly.Python is case sensitive so the use of
NAME
here also led to some confusion for me.The text was updated successfully, but these errors were encountered: