Fix python3-ism with byte v. str

[rustyhowell]

Also make the example in the README a bit more universal.

[googlebot]

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 your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
• In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

[rustyhowell]

I signed it!

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

[coveralls]

Coverage decreased (-0.9%) to 47.193% when pulling 5de7928 on rustyhowell:rhowell_python3 into cb4ae46 on google:master.

[fahhem]

The tests failed because the % will convert a bytes string to "b\'<original string>\'", which isn't expected (and wrong). If you fix that, I'll merge it ASAP

[fahhem]

Ping? Is this worth merging still?

[rustyhowell]

I believe this is fixed. You should be able to merge it.

[fahhem]

Is this necessary with #128 merged in?

[rustyhowell]

Probably not anymore. It looks like #128 has my changes in it.