Python for humans

A nice, if overly Pythonic, presentation about how to structure things better for the coder in complex areas like HTTP retrieval.

Here's the thing. Python's standard HTTP retrieval is a horrible mess because it provides options for every eventuality - and in Python, we all know that There's Only One Right Way.

This is ludicrous.  I see where they're coming from, but it holds them back.  There are always a multitude of Right Ways for something as inherently as complex as HTTP retrieval.  Sometimes you need those nasty callbacks.  And sometimes - arguably, most of the time - you really don't.  Insisting that all use cases always have to be identical is ridiculous.  We don't do that in the real world or in natural language, so why force it further than it should go in a programming language?

This is the sort of thing that should be documented in some kind of literate macro style or something, with wrapper objects or something of that nature.