[efsavage]

I don't mean to badmouth Requests or Python in general, it certainly looks like an improvement, but can anyone enlighten me as to why an API that wraps an HTTP request with concise methods is #1 on HN, twice? This looks more like a good answer to SO question than "news".

This looks like all the other wrapper methods you spend 5 minutes doing, once, when you start a new codebase?

[mcav]

It's #1 because people vote it up; people vote it up because it interests them or they'd like to see more of it. That's the pattern for every link here.

We may agree or disagree with the consensus of the masses, but the masses make the front page.

[lukeschlather]

The philosophy of Python is that those wrapper methods shouldn't be necessary.

I'm glad when language quirks and libraries get linked, it's good for discussion. (And more informative than a good third of the stuff that gets linked.)

[drgath]

I came here with the same question. Considering I come from PHP & JavaScript where the native APIs are awful, wrapping is a necessary step for sanity. Interesting that Python didn't have this until now.

[lukeschlather]

Python has always had it to some degree, but merging these sorts of things into the core language is what major releases are for. No language is perfect. I think the reason you see this upvoted so much is there are so many Python programmers who want to see this on the roadmap for future versions of Python (and it probably will be.)

[kenneth_reitz]

I couldn't agree more.

I gave a talk about this very thing at PyCodeConf this week. Here are the slides: http://python-for-humans.heroku.com

[toyg]

Maybe because doing the same wrappers over and over again, as short as they might be, is boring?

[tomp]

The design of this library reminds me of Apple's design... While a lot of Python is more like Google, or Microsoft - they just don't get it. (Admittedly, parts of Python are very well-designed, but I still see a lot of room for improvement...)