Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialdavigarcia
2,590 PointsUnable to use " or ' characters on Python console at Workspaces
For some reason I'm unable to use the characters ' and " on console. pressing these symbols on my keyboard does not show anything on console. But works properly on editor, at the same workspace.
4 Answers
davigarcia
2,590 PointsYeah! This is the bug, the keyboard source defined as U.S. International (English). I just changed to U.S. (English) and the console accepts the " and '. This is probably because he is evaluating " and ' as accents (like Γ‘, Γ and Γ’, for my native language).
Kenneth Love
Treehouse Guest TeacherWeird. Just tried it here and no problems. What browser are you using?
davigarcia
2,590 PointsI'm using Firefox 30.0 on Mac OS X 10.9.4. The only detail is that I loaded the Workspace URL on a tab, instead of use the pop-up window created by default. I just notice that there is a update to my Firefox, I'll apply and load the workspace normally (pop-up) to check if the problem persists.
davigarcia
2,590 PointsSame issue on Firefox 31.0 and using the Worspace pop-up window (default behavior). By the way, I'm from Brazil and I'm using the keyboard as US International source (I can apply for example ΓΌ = " + u).
Kenneth Love
Treehouse Guest TeacherKenneth Love
Treehouse Guest TeacherWell, glad you found it. I've sent it to our Workspaces team, though, since, ideally, we'd work with whatever your encoding is. I tried Firefox 31, in a tab instead of popup, and had no problems. Just for the record.
Weird bug. Thanks for finding it!