roywashereWhy I forked httpx
the http landscape is rather scary lately in Python. instead of forking join forces... See Niquests https://github.com/jawah/niquests
I am trying to resolve what you've seen. For years of hard work.
The basis of httpx is not very good at all.
I think that it owes its success to be first "port" of python requests to support async, that was a strong need.
But otherwise it is bad: API is not that great, performance is not that great, tweaking is not that great, and the maintainer mindset is not that great also.
For the last point, few points were referenced in the article, but it can easily put your production project to suddenly break in a bad way without valid reason.
Without being perfect, I would advise everyone to switch to Aiohttp.
It is indeed a shame that niquests isn't used more, I think trying to use the (c'est Français) argument to in French will bring you many initial users needed for the inertia
Is it knee-quests or nigh-quests?
I've started seeing these emoji-prefixed commits lately now too, peculiar
There is a series of extensions for Vscode that add this functionality like https://github.com/ugi-dev/better-commits
GitHub - ugi-dev/better-commits: Powerful Visual Studio Code extension that enforces standardized commit messages, ensuring convention and consistency across Git repositories.
Powerful Visual Studio Code extension that enforces standardized commit messages, ensuring convention and consistency across Git repositories. - ugi-dev/better-commits