-
Notifications
You must be signed in to change notification settings - Fork 400
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
Expose Python exceptions in public module #1771
Comments
@Simske, that would be great. The exceptions were actually meant to be public :). Personally I would go for the dedicated submodule approach. |
@roeap I checked but they are already available under the exceptions module |
well - even better :). @Simske, could you confirm that works for you? |
I'm closing this since have it already in the exceptions module. |
I'm not sure how I overlooked that - thank you. |
Description
The
deltalake
-Python module defines multiple exceptions which can be raised when working with the package (DeltaError
,TableNotFoundError
,CommitFailedError
,DeltaProtocolError
). However these exceptions are defined only in the "private"deltalake._internal
submodule, and not in the root module or a public submodule.As I don't expect the interface of
._internal
to be stable it would be useful to expose them in a public module with a stable interface.My suggestion would be to either:
exceptions
I'm happy to open a PR for this.
Use Case
The user needs to import the exceptions if they want to do speficic exception handling, e.g.
Related Issue(s)
None
The text was updated successfully, but these errors were encountered: