Count/ScannedCount support for dynamodb.layer2.(scan|query)
add count argument to dynamodb.layer1.query()
fix consumed_units to match Amazon return value (float)
add value to get/set remaining generator iterations
add ability to jump ahead in result set pagination
add ability to query for meta-data values before iterating
oops; fixing broken max_results=0 behavior
make dynamodb.table.(scan|query) track layer2.(scan|query) perfectly
fix tests to correctly use keyword arguments in scan/query calls
PEP8
This change constrains requests made by the scan
and query TableGenerators according to any limit
of the generator.  This can result in dramatic
speed and read_unit efficiency gains.
update the tests for new generator behavior
optional tweaks for backwards compatiblity
Merge branch 'scan_query_count' of git://github.com/disruptek/boto into disruptek-scan_query_count