Issue #1636
closedDeveloper oriented error messages have been added as coded exceptions
Description
A good reason not to put developer errors in the "coded exceptions" is that the coded exceptions need to be well documented and communicated to the users. As these users include our API consumers who may wish to respond to our error code, this will cause them to spend time thinking about how to handle a problem they will never experience. Let's save them the time by just raising a normal boring old Python Exception (or the subclass that makes the most sense). Also, it's probably not necessary to use gettext since working on our code already implies that developers know English enough to read/write our docblocks and comments and variable/function names ☺
We should check for this in all plugins too. We need to do this before we release 2.8.0 because some of these were introduced new in 2.8 and once we release we have to keep it.
Updated by sbhawsin about 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to sbhawsin
Updated by sbhawsin about 8 years ago
- Status changed from ASSIGNED to POST
Added by sbhawsin about 8 years ago
Added by sbhawsin about 8 years ago
Revision db4ded65 | View on GitHub
Issue 1636: Developer oriented error messages added as coded exceptions
https://pulp.plan.io/issues/1636
closes #1636
Updated by sbhawsin about 8 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|db4ded6575fd9bd503f74633a17e13a46c8d95c9.
Updated by dkliban@redhat.com about 8 years ago
- Status changed from MODIFIED to 5
Updated by dkliban@redhat.com about 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Issue 1636: Developer oriented error messages added as coded exceptions
https://pulp.plan.io/issues/1636
closes #1636