The other day I "heard" someone mentioning `niquests` as a replacement for `requests`:
https://pypi.org/project/niquests/
"It is a drop-in replacement for Requests, which is under feature freeze [...] is the “Safest, Fastest[^10], Easiest, and Most advanced” Python HTTP Client"
Meanwhile `requests` made a release after. Is this some kind of typosquatting? What do we know about `niquests` real reason to fork and/or reimplement?
@mdione it looks pretty legit to me. Requests is basically a static target now which I’d usually consider fine for an HTTP client library but it really sucks not to have asyncio and types in what is the defacto HTTP client for Python so I’m glad to see options springing up.
@jon Why "static target"? Did the developers decide they won't add more features (which is fine, really)?
@mdione yes, which as I say is fine, but the features they’re not interested in adding are really table stakes for me wanting to use a library these days. Untyped code for something like this feels like going back to the stone ages now as I try to guess what parameters a function wants from nothing but the name.
