Big time test failure here. Do you know why?

I ran the tests in a different shell, which I closed accidentally before committing. :(

I will rebase / fix after merging #876.

@dhermes rebased.

So the reason I asked you to peel this off from #876 was really so we could discuss if this should happen.

I have never really liked the methods, but some may like them. So let's discuss?

To clarify what we are discussiing: first, we are removing:

if blob_name in bucket:
   do_something()

which is a syntactic alias for:

blob = Blob(blob_name, bucket)
if blob.exists():
    do_something()

Note that do_something() likely needs to construct the Blob anyway, which makes the second a lot more natural. The second form also allows us to override the connection used by the exists() call, if desired.

Second, we are removing:

for blob in bucket:
    do_something(blob)

which is a syntactic alias for:

for blob in bucket.list_blobs():
    do_something(blob)

Here, the list_blobs() form allows us to override the connection used, if desired, as well as providing filtering parameters to minimize the set of returned blobs: the latter could be crucial for dealing with very large buckets.

@jgeewax Are you OK with us removing this?

I am on-board with this change.

I'm down with removing the methods, but we need to update the docs in the same PR, right? (https://googlecloudplatform.github.io/gcloud-python/latest/storage-buckets.html refers to for blob in bucket and print 'blob' in bucket.)

+1

@jgeewax 3a3edb4 removes the docstring examples which referred to the sugar.