Adding wait_other_notice=True for ccm
Better messages and docs for Read/WriteTimeouts
Fix memory leak when destroying libev connections

The IO objects held a reference to their LibevConnection instances
through the callback.  This reference cycle was preventing the
connection from being garbage collected.

Fixes #93
Minor tweak to Read/WriteTimeout error summaries
Ensure token map is rebuilt when nodes are removed
Release 2.0.2
Make version 2.0.2.post
Fix changelog typo
dict_factory docstring fix
docstring fix
Document exceptions moving from cassandra.decoder to cassandra.protocol
Merge pull request #136 from dizpers/patch-1

dict_factory docstring fix
Merge pull request #137 from stanhu/document-exception-changes

Document exceptions moving from cassandra.decoder to cassandra.protocol
Use six.moves for references to xrange

Fixes #138
BoundStmt should inherit fetch_size from PreparedStmt

Fixes PYTHON-80
Use ev_loop_new and ev_loop_destroy

Related to #141
Cleanup live watchers during libev loop cleanup

Relates to #141
Add methods for cleaning up after forking

Relates to #141
Detect fork in child proc, reinitialize reactor state
Replace six.BytesIO with io.BytesIO for speed-up

On python 2.6 and 2.7, six.BytesIO maps to StringIO, which is slow:

https://github.com/kelp404/six/blob/master/six.py#L478

Python 2.6 and 2.7 provide the io module (for compatability with
the Python 3 io module), which defines a faster BytesIO implementation.
cProfile reveals a significant speedup when using the io module. Using
six.BytesIO:

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
  ...
  2277792    9.736    0.000   13.088    0.000 /usr/lib64/python2.6/StringIO.py:208(write)

However with io.BytesIO:

  2277792    0.920    0.000    0.920    0.000 {method 'write' of '_bytesio._BytesIO' objects}

This will break on Python 2.5, but I think that's ok.