We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would be great to have a single "base" class for all errors that could be raised by the library.
Looking at https://github.com/stub42/pytz/blob/master/src/pytz/exceptions.py, there are two base classes at the moment: UnknownTimeZoneError and InvalidTimeError.
UnknownTimeZoneError
InvalidTimeError
Without a guaranteed single base class, a package upgrade may add new error types, without call-sites being updated about the change.
The text was updated successfully, but these errors were encountered:
Agreed. I'm surprised they don't already share a base class.
Sorry, something went wrong.
238b4f6
Thanks for taking care of this, @stub42! :)
No branches or pull requests
Would be great to have a single "base" class for all errors that could be raised by the library.
Looking at https://github.com/stub42/pytz/blob/master/src/pytz/exceptions.py, there are two base classes at the moment:
UnknownTimeZoneError
andInvalidTimeError
.Without a guaranteed single base class, a package upgrade may add new error types, without call-sites being updated about the change.
The text was updated successfully, but these errors were encountered: