Skip to content
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.

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

input against raw_input is not really explicit #7

Open
gnunicorn opened this issue Sep 29, 2013 · 1 comment
Open

input against raw_input is not really explicit #7

gnunicorn opened this issue Sep 29, 2013 · 1 comment

Comments

@gnunicorn
Copy link
Member

I had a few people running into problems with the whole input vs. raw_input. And because the code itself worked but then it broke when the user typed stuff in, it wasn't obvious to me as a coach, why this is breaking. Instead of using raw_input a few actually typed "left" with quotes and it worked. But is weird.

@Ivoz
Copy link
Member

Ivoz commented Sep 29, 2013

Well "left" given to python 2's input() is equivalent to left given to python 3's input(), so it makes sense. I thought the note should be pretty clear - is there anything you can suggest we could do to clarify?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants