You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
espidf.IDFError is a subclass of OSError, which is a subclass of Exception. raise_esp_error() is a general routine that is used to check ESP-IDF error codes and raise espidf.IDFError with an appropriate message.
There are a number of non-ESP-specific contexts in which this error is raised, such as AnalogIn, neopixel_write, PulseOut, etc. where something like RuntimeError would be more appropriate, because the error is something that doesn't need to be designated as ESP-IDF-specific.
I am wondering whether we should change the type of the raised exception, or whether we might make IDFError be a subclass of RuntimeError instead, because many of the errors are not "OS"-related.
The text was updated successfully, but these errors were encountered:
espidf.IDFError
is a subclass ofOSError
, which is a subclass ofException
.raise_esp_error()
is a general routine that is used to check ESP-IDF error codes and raiseespidf.IDFError
with an appropriate message.There are a number of non-ESP-specific contexts in which this error is raised, such as
AnalogIn
,neopixel_write
,PulseOut
, etc. where something likeRuntimeError
would be more appropriate, because the error is something that doesn't need to be designated as ESP-IDF-specific.I am wondering whether we should change the type of the raised exception, or whether we might make IDFError be a subclass of
RuntimeError
instead, because many of the errors are not "OS"-related.The text was updated successfully, but these errors were encountered: