Turbogears2 migration: API calls

[Thomas De Schampheleire]

On Sun, Sep 18, 2016 at 12:23 PM, Alessandro Molina
<alessandro.molina at gmail.com> wrote:
>
>
> On Sat, Jul 30, 2016 at 10:01 PM, Thomas De Schampheleire
> <patrickdepinguin at gmail.com> wrote:
>>
>> Hi,
>>
>> API calls currently do not work under Turbogears2.
>>
>> The simplest call is:
>>
>> ../venv/kallithea-tg-clean/bin/kallithea-api
>> --apikey=811a4ad6f382e75c20392b668cad9408bde9f42e
>> --apihost=http://localhost:5000 test
>>
>> (where apikey can be obtained from the web UI, after logging in, going
>> to 'My account' via you user name top right, then API keys.)
>
>
> Hi Thomas,
>
> I made a proof of concept of working APIs, I tried to keep it to minimum
> changes so it suffers of `self.something=` issues but seems it's able to
> receive requests, respond and report errors.
>
> See it at
> https://bitbucket.org/_amol_/kallithea-tg/commits/ead627a07f0c30961772985a441d9ef574c4b061
>
> It will require tgext.routes>=0.2.0 which I changed to allow mixing multiple
> routing systems as required by Kallithea RPC APIs
>

I applied this patch on top of the latest stack, tried a few API
calls, and indeed it seems to work fine. All API tests also pass now.

So things look very good now, thanks a lot!

Best regards,
Thomas