Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). 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 (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

CLAs look good, thanks!

The raw_input function isn't available in Python 3.6 (and the Travis build failed). Perhaps add a different codepath for Python 2 and 3?

If it weren't possible to add two different codepath in order to explain the issue with Python2, it would be useful adding a comment with the correct version.

Any update to this PR?

There haven't been any updates in the last 10 days. I suppose I have to change the code by adding the comment that explains the issue with Python 2.7 and then ask for a new pull request. Am I right?

I don't think this PR fixes an issue with inputs.
https://stackoverflow.com/questions/4915361/whats-the-difference-between-raw-input-and-input-in-python3-x

No, this PR tries to avoid users to encounter an input error while running the script with Python 2.x. I suggest to maintain the 3.x code and add a comment to let user know about the possible issue.

@MattiaFailla - See above where it says "Add more commits by pushing to the patch-1 branch on MattiaFailla/python-samples." Commits added that way will be automatically included in this PR; you won't have to create a new one.

Thank you for the clarification! I'll get to work and push changes.

A simple solution, thanks!