temp commit
pre-pep8 cleanup
pep8 cleanup
merge with current master
Allow erlang ad-hoc functions in m/r (allow_strfun)
Merge branch 'master' into pevm-unittest-determinism
convert the last few buckets
Merge branch 'master' into pevm-unittest-determinism
grab bucket property deletion
clearing all properties now, some additional enhancements
add 204 to the list of OK return codes when returnbody=True
make clear_bucket props retryable again.
Switching JSON encoding to UTF-8.

By default, python's JSON encoder will escape all non-ASCII
characters, using a sequence of 6 bytes, for the sake of legacy
non-UTF-8 compatible clients. This is a significant overhead in the
case of non-ASCII string and can be reduced by using a modern encoding.
Merge pull request #205 from Atilla/proper_json

Switching JSON encoding to UTF-8.
Merge pull request #170 from evanmcc/pevm-unittest-determinism

Unit test enhancements
add 204 test
Merge branch 'master' into pevm-204-fix
Merge pull request #206 from basho/pevm-204-fix

add 204 to allowable list for put responses for master
Fixed typo for __ne__

We could probably also refactor `__ne__` to call `__eq__`
Merge pull request #208 from shuhaowu/typo-fixes

Fixed typo for __ne__
Getting rid of RiakLink in favour of tuples

Please review this carefully! There are some potential issues that we
need to address. Before that, some points needs to be noted:

 1. `RiakLink.get` was actually never tested in code.
 2. The new interface should be easier to use in a lot of scenarios
    where you are iterating through links (you can do
    `for bucket, key, tag in obj.get_links()`), it maybe less clear than
    a class. IMO this is not the case as a 3-item tuple is sufficient,
    but if the `RiakLink.get` method is actually used a lot in the wild,
    it might be benificial to include some sort of wrapper function.

A potential issue that I identified: I've noted that `client.index`
doesn't actually perform the Riak 2i operation as specified in the HTTP
and PBC protocal and does a map reduce operation instead. Right now an
index operation actually seems to return links, which seems weird (see
line 110 in riak/test/test_2i.py) as it seems like the Riak API just
returns keys and this is returning `(bucket, key, None)`