Framework for HTTP(S) API?

[NoraCodes]

I'd like to have a consensus on how to implement the HTTP(S) API. I would suggest Flask but that is only because of my inexperience with other options (Bottle, Pyramid, etc).

Once we have a decision on this, a skeleton API could be written with the actual implementation filled in as the functionality materializes. It will mostly be boilerplate and there is no reason for implementers of actually hard things to have to write that code as well.

[Mec-iS]

The trend now seems to be gunicorn with lightweight applications: Python threading or Falcon Framework, I have good experience with webapp2 but I am not sure about future support. Bigger frameworks can be overkilling, it can be preferred to start from server plus basic authentication, Flask can be the choice if frameworks features are needed.

[NoraCodes]

I'm somewhat concerned that webapp2 isn't maintained anymore. It seems to be hosted on Google Code, which is now gone (except for the readonly archive). I'd be happy with gunicorn, since it seems to be quite robust while remaining small (and pure Python!)

[benmoran56]

I would recommend Pyramid framework. http://www.pylonsproject.org/
It can handle small single-file apps like Flask, but offers greater flexibility if the project does grow in the future. Specifically, the configuration is much more flexible.

[Scondo]

Pylons/Pyramid is a full-featured framework with ACL, resource-based URLs etc.
It is good for web-portal, but too big for API in my opinion.

Lightweight framework like Flask or even pure-wsgi (via gunicorn or wsgiref.simple_server) should be much better for API.

[benmoran56]

My mistake, I thought this was in reference to the webui, like go-ipfs has. If it's just the API, then Flask is certainly enough (and quite nice for that).

[jbenet]

• the webui should work on top of the same API.
• i remember flask and bottle being pretty good for APIs