The HTTPbis have spoken, HTTP/2.0 is happening. Major websites are beginning to
adopt it (hello there Twitter!), and the spec is beginning to get nailed down.
If you're unfamiliar with HTTP/2.0 and all the fun things it brings you, Ilya
Grigorik has been doing an excellent job evangelising for it. Take a look at
this talk if you want a deep dive into HTTP/2.0.
If you want a shorter discussion,
this article is also a great
Based on anecdotal data I can safely say that most people view "Open Source" as
roughly synonymous with "Free" (as in beer). And in an impressive number of
cases, that's actually true. Many (maybe even most) open source developers are
happy to give the fruits of their labour away for no cost at all.
Every now and then the Requests project gets bored of fixing bugs and decides
to break a whole ton of your code. But it doesn't look good when we put it
like that, so instead we call it a 'major release' and sell it as being full of
shiny new features. Unfortunately it turns out that people complain if we break
their code and don't provide a nice way to find out what we broke.
This question pops up a lot on Stack Overflow, on GitHub, and in the IRC
channel, so I thought I'd write a short post to address it. The question is,
One of Requests' most popular
features is its simple proxying support. HTTP as a protocol has very
well-defined semantics for dealing with proxies, and this has lead to
widespread deployment of HTTP proxies.