Interesting idea. +1 from me; probably can be as simple as just having the tokenizer interpret curly quotes as the ASCII (straight) version of itself (in other words, " and the two curly versions of that would all produce the same token, and same for single quotes, eliminating any need for additional changes further down the chain). This would help with copying and pasting code snippets from a source that may have auto-formatted the quotes without the original author realizing it.

On Sat, Oct 22, 2016 at 1:46 AM Ryan Birmingham <rainventions@gmail.com> wrote:

I was thinking of using them only as possibly quotes characters, as students and beginners seem to have difficulties due to this quote-mismatch error. That OSX has smart quotes enabled by default makes this a worthwhile consideration, in my opinion.

-Ryan Birmingham

On 22 October 2016 at 01:34, Ethan Furman <ethan@stoneleaf.us> wrote:
On 10/21/2016 10:17 PM, Ryan Birmingham wrote:

I want to start small and ask about smart/curly quote marks (” vs ").
Although most languages do not support these characters as quotation
marks, I believe that cPython should, if possible. I'm willing to write
the patch, of course, but I wanted to ask about this change, if it has
come up before, and if there are any compatibility issues that I'm not
seeing here.

What is the advantage of supporting them? New behavior, or just more possible quotes characters?

--
~Ethan~
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/

_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/