SnapdError is too generic
Bug #1734235 reported by
Leo Arias
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
New
|
Undecided
|
Unassigned |
Bug Description
We have an exception in snapcraft/
This exception should be removed or only be used as a base class. We should add individual exception for each possible error.
summary: |
- SnapdError is too genericc + SnapdError is too generic |
To post a comment you must log in.
Sent from Mailspring (https:/ /link.getmailsp ring.com/ link/local- 78f2527c- 9667@lindon/ 0?redirect= https%3A% 2F%2Fgetmailspr ing.com% 3Fref%3Dclient& recipient= 1734235% 40bugs. launchpad. net), the best free email app for work
On Nov 23 2017, at 11:55 pm, Leo Arias <email address hidden> wrote: internal/ errors. py called SnapdError.
> Public bug reported:
>
> We have an exception in snapcraft/
> This exception is raised in two different contexts, passing a different
> message for each case.
>
> This exception should be removed or only be used as a base class. We
> should add individual exception for each possible error.
Why can't we have one exception that handles the whole thing? Imagine doing that for the store errors, we will go crazy.