Adding back storage.lookup_bucket. #700
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was originally removed in #588.
@tseaver I'd like to remove all the bucket functions from
Connection
and move them intoapi
. WDYT?Also it seems we'd eventually want to add a
_require_connection
as indatastore.api
. It would be nice to come with a re-factor for re-usability (theBatch
is the part which needs to be package specific).FWIW: I came across this while trying to make implicit auth work in storage. Importing
Connection
in_implicit_environ
creates a cycle, essentially becauseConnection
importsBucket
.