Repository navigation
Dataset isn't in the docs as a "concept #707
Description
We added back the Dataset class (basically an alias class that fills in some blanks for you), but it's not listed on the left navigation of the docs. Any chance we can put that back?
If we do, we should add a lovely ..note: banner on that page saying that if you only interact with one dataset (a default one) that you don't need to worry about this, and you can use datastore.<method> and we'll automatically use the default dataset.
Activity
dhermes commentedon Mar 12, 2015
On it.
Secondary bug is that we have no automated way of determining that modules are left out of the api docs. (It's low priority since we seldom add modules.)
dhermes commentedon Mar 12, 2015
Filed #714 and sent an easy fix in #713.
feat: removed pkg_resources for native namespace support (#707)
chore(deps): update dependency google-cloud-bigtable to v2.14.0 (#707)
chore: release 0.37.1 (#707)
feat: add support for asynchronous long running operations (#724)
feat: Add bloom filter related proto fields (only in the preview API …
chore(deps): update dependency google-cloud-bigquery to v3.4.2 (#707)
fix(deps): add pytz as an explicit dependency (#707)
chore: release 1.10.2 (#708)
chore(deps): update dependency google-cloud-bigquery to v3.4.2 (#707)
fix(dependencies): add urllib3 and requests to aiohttp extra (#755)
chore(deps): update dependency grpcio to v1.73.1 (#707)
chore: Set branch protection for python2 branch (#707)