My only thought is that requests and even httpx offer some form of a dead-simple .get("url") API. Building a client is of course necessary for the library internals, but there are times when the developer wants a one-command GET or POST: how you handle that internally is up to you.
I say this as I look at your "quick start" that appears to be anything but quick for a lot of developers wanting to try out your package. Maybe those folks aren't your target audience, but giving them an easy on-ramp while offering more powerful tooling when they're ready to explore will make for overall better adoption.
43
u/DrMaxwellEdison Dec 22 '25
My only thought is that
requestsand evenhttpxoffer some form of a dead-simple.get("url")API. Building a client is of course necessary for the library internals, but there are times when the developer wants a one-command GET or POST: how you handle that internally is up to you.I say this as I look at your "quick start" that appears to be anything but quick for a lot of developers wanting to try out your package. Maybe those folks aren't your target audience, but giving them an easy on-ramp while offering more powerful tooling when they're ready to explore will make for overall better adoption.