require requests 1 and not requests-transition
specify requests < 2.0, until 2.0 comes out and we confirm that it still works
Remove ManagedConnection from the code
Merge pull request #1 from LuminosoInsight/unmanaged

Remove ManagedConnection from the code
Not "infinity"--"zero"!

For some reason, when we told gevent to wait for an infinite amount of
time between calls, it decided that meant "wait no time at all", and
thus the method in question would run whenever gevent yielded. (I think
that's the right term here.) That would be wrong on gevent's part, and it
was fixed in gevent in Python 3, as far as we can tell.

Unfortunately, when we told it to wait for an infinite number of seconds
in this test, we actually *did* want the "0" behavior. So this change
explicitly sets it to that.
Python 3 changes

As always, the usual stuff: "when I say 'range' use 'xrange'", that
sort of thing. Also a change to "callable()"; and it turns out that
the tests want the monkey.patch_all() to be called in setup, and
not before setup.

Also took this chance to remove some debugging print-statements
that were commented out.
remove the callable() checks, because we're not on requests-transition anymore
Updating CLI to not use deprecated "version" in ArgumentParser
Fixes to test, to get it to run reliably

It turns out we really *did* want an infinite delay rather than a zero delay,
which is simulatable by telling it its update seconds is None. Then each test
starts with MONITOR.do_update(), which gets the relevant information into the
relevant places.
(tests) Move the MONITOR.do_update() calls between the events being detected and the checks on the event handlers