require requests >= 1.2.0, fixes #3

there's a problem with redirect handling in requests before 1.2.0, that
caused it to try and work with the future object rather than the "real"
response. it was fixed for another reason, but address this. thanks to
@heston for the report.
version bump to 0.9.4