Refactor exception handling: Define custom exceptions as subclasses of a base Errors class #465
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request refactors the exception handling in
protect_archiver
. The following changes were made:ProtectError
,DownloadFailed
, andAuthorizationFailed
as subclasses of a baseErrors
class inerrors.py
.download_file.py
to correctly import these exceptions.Changes
errors.py
: DefinedProtectError
,DownloadFailed
, andAuthorizationFailed
as subclasses ofErrors
.download_file.py
: Updated import statements to use the newly defined exceptions.Motivation and Context
This refactor resolves the following issues:
AttributeError: 'NoneType' object has no attribute 'get'
None
being accessed incorrectly.TypeError: catching classes that do not inherit from BaseException is not allowed
BaseException
. The new hierarchy ensures that all custom exceptions are correctly defined as subclasses ofErrors
, which inherits fromException
.How Has This Been Tested?
download_file.py
and other modules import and use the exceptions without issues.