Embrace the APIs of the future. Hug aims to make developing APIs as simple as possible, but no simpler.
First off thanks for this framework, it was a super nice experience to get started here. Now I have found myself in a conundrum: I have a construct where I give my hug api a presigned URL. Hug seems to end up swallowing the signature however:
import hug
@hug.post("/adler32")
def test(url):
return str( url)The result looks like this:
curl http://localhost:8000/test -d url="https://some.s3.bucket/file?AWSAccessKeyId=XXX&Signature=YYY&Expires=123456789"
"https://some.s3.bucket/file?AWSAccessKeyId=XXX"%Where does the signature slug get munched up?
hi folks. i'm trying to make a custom output format which encodes as CBOR:
import hug
import cbor
@hug.format.content_type('application/cbor')
def cbor_format(data, request=None, response=None):
return cbor.dumps(data)
@hug.get(format=cbor_format)
def test(request, response):
return request.headersbut my cbor_format is not called and the data delivered as text/plain. i'm a hug noob so probably just misunderstanding something.
(venv) estan@edison:~/test$ curl http://localhost:8000/test
{"CONTENT-LENGTH": "", "CONTENT-TYPE": "text/plain", "HOST": "localhost:8000", "USER-AGENT": "curl/7.58.0", "ACCEPT": "*/*"}
import hug, json, io
from hug.types import text
from hug.types import json as hugJson
class AccessAndLoggerMiddleware:
def process_resource(self, request, response, resource, parameters):
rawData = request.stream.read()
stream = io.BytesIO(rawData)
request.stream = stream
print('User: {}'.format(json.loads(rawData).get('user')))
hug.API(__name__).http.add_middleware(AccessAndLoggerMiddleware())
@hug.get('/test')
def test(user:text, key:text, content:hugJson, request, response):
return "Test"
I'm looking to use hug to expose an API for long running tasks, and I saw a post here and an issue on github mentioning celery... I wonder if someone has a working example on how to get it working.
I was thinking about a wrapper/decorator on top of hug.post, let's call it hug.post_async, that handles the call the celery task, and returns a 202 response with the url of a job status endpoint. Can it be done?
hug -f myapp -c myroute in this gitter history... but who wants to add hug -f to every command? not me. So was going to ask how to modify the shebang so I can just do myapp -c myroute but a quick google search gave me the solution. So just a FYI in case anyone else wanted to do this. This worked for me:#!/bin/sh
''''exec hug -f "$0" ${1+"$@"} # '''#!/usr/bin/env python line at the top of your program with that.
Hi @timothycrosley !
I was wondering whether a new Hug version was planned / in the works that would take advantage of Falcon 3.0+?
I've tried running Hug's test suite with 3.0.0, and it seems the biggest breaking change causing multiple failures is the default Exception handler, that is always added to the app, unless the user provides their own, of course. The default handler no longer bubbles up the exception to the app server, but renders an HTTP 500 response.
I'm happy to answer any Falcon questions if needed, but OTOH I don't know that much about Hug's internals, so it wouldn't be me doing any advanced porting.
Furthermore, Falcon 3.0 adds optional ASGI support, so Hug could implement true async support, WebSocket, SSE etc. Also added was native multipart form parsing, and simple CORS support out of the box.
