Current offenders:

1. There is no way to allocate_ids without explicitly using protobufs. I have partially addressed (Implemented in Adding a non-protobuf allocate_ids method on Dataset. #436).

2. Transactions don't give any indication of success or failure (i.e. commit or rollback in __exit__). (Filed DISCUSSION: Is there a way for a Transaction to indicate success/failure from __exit__ #496)

3. Query (and other classes) could be more Pythonic by allowing us to pass values to constructor that also have their own setters. For example:

   query = dataset.query('Character').ancestor(
       ANCESTOR_KEY).limit(10).order('appearances')

   becomes

   query = dataset.query('Character', ancestor=ANCESTOR_KEY,
                         limit=10, order='appearances')

   We don't have to go as extreme as DISCUSSION: Are setter methods which clone and return object type confusing to end-users? #188 by wiping away the return self behavior in the setters, but could use them in conjuction with more Pythonic constructors. (Implemented in Fix #439: split query vs. iterator apart. #487)

4. Query.cursor() should not raise an error before being used. Using query.cursor() is None gives a way to check progress in a query. For example, in paging: (addressed in Removing cursor and more results from query object. #432)

   query = dataset.query(kind=kind).limit(FETCH_MAX)
   results = []
   more_results = True
   while more_results:
       # Make new query.
       if query._cursor is not None:
           query = query.with_cursor(query._cursor)
   
       curr_results = query.fetch()
       results.extend(curr_results)
   
       more_results = len(curr_results) == FETCH_MAX

5. Query should give access to start_cursor and end_cursor. It is currently only set on the pb. (see Removing cursor and more results from query object. #432)

6. Comparing Entity values should be easier. Current workaround is

   arya_dict = dict(arya_entity.items())
   self.assertEqual(arya_dict, {'name': 'Arya', 'family': 'Stark'})

7. Paging with offsets should be a bit more automatic, as it is in gcloud-node. Currently we have to

   query = query.offset(offset).limit(limit)
   entities = page_query.fetch()
   # Offset needs to be reset to 0 since we want to start exactly at `cursor`.
   next_query = query.with_cursor(cursor).offset(0)

   (done in Fix #439: split query vs. iterator apart. #487, since offset always defaults to 0)

8. I'm sure there will be plenty more to come after Implementing storage regression tests to match gcloud-node. #319

9. (UPDATED): Consider making bulk-adding properties to Entity more intuitive. See update() override for datastore entities #389. (dict.update() is Pythonic and simple to use / multi-type signature)

10. (UPDATED): "Creating a new datastore.entity with a key name is a pain." See Creating a new datastore.entity with a key name is a pain #82