[ckan-dev] API docs update

[David Read]

I agree with Sean's criticisms with ckanclient - it has become a bit
overgrown over the years and is definitely due for restarting from
scratch. I suggest you call the new one 'ckanclient2' and leave the
old one there marked as deprecated.

No doubt the old client will still be useful to some people. And even
if no-one else uses the RESTful APIs v1 & v2, I will continue to use
them for their simplicity...

Dave

On 8 February 2013 17:03, Peder Jakobsen <pjakobsen at gmail.com> wrote:
>
> On 2013-02-08, at 4:59 AM, Sean Hammond <sean.hammond at okfn.org> wrote:
>
> I would love to work on ckanclient as I think it'd be easy to write a
> few lines of Python code that would let you post a python dict to any
> action api function and get a python dict back, with just a single
> python function call (https://gist.github.com/seanh/4130567A), which
> would be a really convenient way to use the CKAN API, and then you could
> do cool stuff with it like implement an interactive CKAN API shell.
>
>
> Agree, a new client API would be useful, something really small and simple
> yet with good errors messages and various utility functions.
>
> When I began working on CKAN, I quickly abandoned the CKAN Client because 1)
> I needed better visibility under the hood 2) because writing JSON apps is
> dead simple in Python.
>
> Just my 2 cents worth,
>
> Peder
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>