[ckan-dev] A new ckan client library: ckanapi
Ian Ward
ian at excess.org
Mon Apr 15 18:06:37 UTC 2013
On Mon, Apr 15, 2013 at 1:38 PM, Toby Dacre <toby.okfn at gmail.com> wrote:
>
> On 15 April 2013 17:18, Ian Ward <ian at excess.org> wrote:
>>
>> Are you suggesting I convert the exceptions that CKAN raises to my own
>> copies of them in the "local CKAN" case? .. doing something like
>> checking the name of the exception?
>
>
> This might be the best way forward
To me that seems like a bunch of fragile code that will be attempting
type checking based on __class__.__name__, then trying to copy all
the relevant data (which is different for each exception) from one
object to another with the same name, and all this only for the "local
CKAN" case.
Why not make exceptions that actions raise part of their published
interface, with known import locations instead?
Ian
More information about the ckan-dev
mailing list