httpx VS Niquests

Using the createSession, deleteSession endpoints and httpx, we can create a session for API interaction.

I've mostly ditched requests in favour of httpx these days. https://www.python-httpx.org

Now that your environment is set up, you’re going to need to install the HTTPX library for making requests, both asynchronous and synchronous which we will compare. Install this with the following command after activating your virtual environment:

Now time to code the implementation, as I wanted to both read from and write to ffmpeg concurrently, so this is going to be an asyncio application. The http client library we are using this time is httpx, which has a method to fetch download in smaller batches:

The concept of a Client in httpx is analogous to a Session in requests. However, httpx.Client is more powerful and efficient. You can read the article from the httpx documentation, to learn more about httpx.Client.

Let's look at a simple code example. This will work for requests, httpx, and aiohttp with a clean installation and no extensions.

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 ~

I’ve been using niquests with Python. It supports HTTP/3 and a bunch of other goodies. The Python ecosystem has been kind of stuck on the requests package due to inertia, but that library is basically dead now. I’d encourage Python developers to give niquests a try. You can use it as a drop-in replacement for requests then switch to the better async API when you need to.

https://niquests.readthedocs.io/en/latest/

Just around my intent to give up on urllib3 evolution, we proposed a fork of both urllib3 and Requests, namely urllib3-future and Niquests.

Source: https://github.com/jawah/niquests PyPI: https://pepy.tech/project/niquests Docs: https://niquests.readthedocs.io/en/latest/