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.

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

Overhaul the Error system #278

Open
ewu63 opened this issue Dec 22, 2021 · 0 comments
Open

Overhaul the Error system #278

ewu63 opened this issue Dec 22, 2021 · 0 comments

Comments

@ewu63
Copy link
Collaborator

ewu63 commented Dec 22, 2021

Description of feature

The current setup is not very good---we use the same Error class for all exceptions, which means we cannot catch specific errors. Instead, we must resort to parsing the error message as done in #277. We should probably switch to built-in exceptions for most things, and create specific classes for pyOptSparse-specific errors such as not finding the compiled library. We lose the formatted box, but I don't think that's a big deal.

Potential solution

  • switch back to built-in exceptions for most cases, remove the Error class
  • create specific exception classes as needed for when the built-in exceptions are not sufficient
@gawng gawng self-assigned this Feb 18, 2022
@gawng gawng removed their assignment Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants