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
{{ message }}
Repository navigation
NotFoundError is not raised, but Python FileNotFoundError is raised #197
Noticed this while making an integration in dagster (dagster-io/dagster#27450), is that NotFoundError is not raised when you try to do obs.head(), you actually get the standard FileNotFoundError exception. Not sure if this was intended? But it threw me off for a second, since I imported the notFoundError from the execptions module : )
I don't think it's currently possible to do multiple inheritance of exceptions in pyo3 PyO3/pyo3#4979
At this point I think it's more likely that we remove our own NotFoundError and standardize on FileNotFoundError and just document that it's the primary error variant that doesn't subclass from BaseError
Activity
kylebarron commentedon Feb 3, 2025
We can standardize on the obstore exception. Would you like to submit a PR?
kylebarron commentedon Jun 18, 2025
I don't think it's currently possible to do multiple inheritance of exceptions in pyo3 PyO3/pyo3#4979
At this point I think it's more likely that we remove our own
NotFoundErrorand standardize onFileNotFoundErrorand just document that it's the primary error variant that doesn't subclass fromBaseError