httpx VS quart

For reference, it's a butterfly, not a moth.

Source: https://github.com/encode/httpx/issues/834

Very cool, first I'm hearing of httpx https://www.python-httpx.org/

I think most people would start with trying out requests or something for this kind of work, I'm guessing that didn't work out? You've got a star from me.

To access 10 different commands at the same time, that is tricky but definitely doable.

First thing that comes to mind, you can use aliases.

To keep it simple, lets use 3 examples instead of 10: harlequin (this project), pgcli (https://www.pgcli.com/) and httpx (https://www.python-httpx.org/)

Setup a main home for all your venvs:

    cd ~

There are already some implementations for Python HTTP clients. One of them is aiometer. But it's not suitable for my use case. Since httpx already has the internal pool, it would be better to reuse the design.

Besides, flama also provides support for SQL databases via SQLAlchemy, an SQL toolkit and Object Relational Mapper that gives application developers the full power and flexibility of SQL. Finally, flama also provides support for HTTP clients to perform requests via httpx, a next generation HTTP client for Python.

We can use the async HTTP client provided by httpx, a fully featured HTTP client for Python with an API broadly compatible with requests, so it can be used in pretty much the same way in most cases.

httpx in place of requests library

The main value of Requests is that it provided an abstract interface on top of HTTP, which was designed well-enough to become a standard. But today it has fallen way behind in its field, and there are much better alternatives such as HTTPX [0].

[0] https://www.python-httpx.org/

HTTPX is a popular Python library that provides an asynchronous HTTP client, and it can be beneficial for enabling async support in Django. While Django itself does not require HTTPX for async support, using HTTPX in combination with Django's async views can bring several advantages:

The underlying library for both sync and async is httpx (https://www.python-httpx.org/) which may be limited from the HTTP Client perspective but it may be possible to add rate limiting at a Session level.

Sorry. It's not Quartz, it's just Quart https://pgjones.gitlab.io/quart/

If you're looking for an experience that's very similar to Flask you can use Quart which is inspired by Flask. Quart even has a guide about how to migrate from a Flask application to using Quart! Flask's own documentation for async views actually recommends using Quart in some cases due to the performance hit from using a new event loop per request.

Flask getting async support is a huge step for the asyncio web ecosystem in Python. I wonder how Flask's ASGI support will evolve in parallel with Quart[1] which bills itself as the ASGI version of Flask and is maintained by a member of the Pallets team. One of the maintainers of Werkzeug even recommended using Quart[2]

[1] https://pgjones.gitlab.io/quart/

[2] https://github.com/pallets/werkzeug/issues/1322#issuecomment...

What we get with the async part of this release - If you would like to run an async library or your own async code from a flask route you can do that now. This is super useful, where let's say we have some async code that fetches data from many sources concurrently, or call multiple a few ML prediction endpoints at the same time (as long as they don't time out) using httpx and respond with some sort of outcome, or finally try that cool new async-only database library. A current (v2) limitation is that the you can't make concurrent requests using just the current asyncio implementation (an alternative with Flask API and ASGI: Quart). Typically in production gunicorn or uwsgi + threads/processes/gevent-eventlet is used and this makes Flask behave asynchronously. More here and here if interested.

For people looking to do async stuff with Flask, there is also Quart! It’s essentially an async port of Flask, with all your favorite, familiar methods!

I agree with the transition issues, Quart has this awkward code to try and get around this.

Appreciate the feedback! I forgot to pimp my favorite web framework, Quart, but I can attest to Flask and even Django being great. I always looked down on Django as too big but then I used it for my current company and I realized I was totally wrong. Easy to pick up, lots of functionality if you want it, but it doesn't force it on you.