Skip to content

Update README.rst #1805

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
tseaver merged 1 commit into from
May 17, 2016
Merged

Update README.rst #1805

tseaver merged 1 commit into from
May 17, 2016

Conversation

@davidraleigh
Copy link
Contributor

@davidraleigh davidraleigh commented May 17, 2016

Returns None:

blob = bucket.get_blob('/remote/path/to/file.txt')

Returns blob:

blob = bucket.get_blob('remote/path/to/file.txt')

@davidraleigh
Update README.rst
436ac4d 
Returns ```None```:
```python
blob = bucket.get_blob('/remote/path/to/file.txt')
```

Returns blob:
```python
blob = bucket.get_blob('remote/path/to/file.txt')
```
@googlebot
Copy link

googlebot commented May 17, 2016

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@googlebot googlebot added the cla: no This human has *not* signed the Contributor License Agreement. label May 17, 2016
@tseaver
Copy link
Contributor

tseaver commented May 17, 2016

LGTM.

@jgeewax this is certainly not an issue where copyright assignment would matter: do we need to wait for CLA to be happy before merging?

@davidraleigh
Copy link
Contributor Author

davidraleigh commented May 17, 2016

I signed it!

@googlebot
Copy link

googlebot commented May 17, 2016

CLAs look good, thanks!

@googlebot googlebot added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels May 17, 2016
@tseaver tseaver added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. docs labels May 17, 2016
@tseaver tseaver merged commit b449451 into googleapis:master May 17, 2016
@tseaver
Copy link
Contributor

tseaver commented May 17, 2016

Thank you for the patch!

@jgeewax
Copy link
Contributor

jgeewax commented May 19, 2016

@dhermes : In general, the safe bet is to get a CLA signed on everything. I agree it seems silly to require this for things like typo fixes, but it's still important.

@dhermes dhermes mentioned this pull request Jun 7, 2016
Merged
parthea pushed a commit that referenced this pull request Nov 26, 2025
@nbayati
fix: fix type error in credentials.py for python 3.7 and 3.8 (#1805)
dccad5e 
* fix: fix type error in credentials.py for python 3.7 and 3.8

* fix linting error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

cla: yes This human has signed the Contributor License Agreement. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@davidraleigh @googlebot @tseaver @jgeewax