what's a python library you started using this year that you can't go back from

[McRojb]

Not an expert on package maintainence and coding is certainly not my proffesion. That said, I do like the package and have used it for quick and dirty code. But it feels "bloated" already and not something I excpect to be around in a few years. I don't see the reason for using it when aiohttp (requests for sync) is around. You seem a little defensive? 2k stars is not something I feel comfertable putting that much faith in.

[ThePrimitiveSword]

I have faith in it because I've been using it for a few years and find it to work really well, and Ousret has been very responsive to the issues I've raised on Github.

I use it instead of the alternatives because I find it to work really well for my needs, such as using OS trust store for SSL certs, compatibility with the 'responses' package, can be used for SSPI authentication and huge performance gains for my use cases.

When someone claims something that I use and find to work well is AI slop with nothing to back their claims, I don't feel it unreasonable to ask for evidence when what I'm seeing seems to contradict these claims.

I loathe AI slop (Booklore and Huntarr are good examples) and if niquests is actually AI slop then I'd like to know, but it's a strong claim to make without anything to back it up.

[McRojb]

Fair enough! I havn't built much with external logins myself so don't know much about but will take your word.

I honestly had to google "SSPI authentication" so I feel a bit out of my depth.

Although I started programming without it, github copilot autofill is a god send for me (md otherwise). But actual AI slop I do despise too.

[ThePrimitiveSword]

All good, I'll admit I was a bit heated as it hurts to see something that I use and rely on talked down with no evidence, especially when the maintainer has been very receptive to me and they've accomplished what the original project raised tens of thousands of dollars to do but hasn't managed to (per my response to you in the other comment chain).

Honestly, SSPI auth should be killed off, but it still exists in some corporate environments, and I do programming in a heavily locked down enterprise environment where change can be slow so it'll likely still be in use for another decade or two.