This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Quote-type recognition bug [badly fixed last time]
Type: Stage:
Components: Versions: Python 3.0, Python 2.4, Python 2.3, Python 2.2.3, Python 2.6, Python 2.2.2, Python 2.5, Python 2.2.1, Python 2.2, Python 2.1.2, Python 2.1.1, 3rd party
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: chester, gvanrossum
Priority: normal Keywords:

Created on 2008-05-11 19:17 by chester, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg66652 - (view) Author: Chester (chester) Date: 2008-05-11 19:17
I have a suggestion that would make the
http://svn.python.org/view?rev=63068&view=rev look ever more clear. It
would be better to have this kind of error messages:

expect = "End of line while scanning string (<string>, line 1)"

and

expect "End of f... while scanning multi-line string (<string>, line 1)"


These messages really need to be clear, so putting EOF for example
(which I really don't know what it stands for) is really mind-bending.
But if changing EOL and EOF to their actual meaning would cause some
problems, then this look nice as well:

expect = "EOL while scanning string (<string>, line 1)"

and

expect "EOF while scanning multi-line string (<string>, line 1)"

The first two proposals look more readable because I think that many
people don't know what EOF stands for (they can guess for EOL though,
but EOF is just mind-bending and wild guessing). I Googled and found no
answer, so I actually don't know what that error message is saying to me.

Also, it would be good, however, to remove the 'triple-quoted string
literal' and name that simply as 'multi-line string'. Simple is better
than complex. :)

Mister Rossum, please give a go on that. I kindly ask you to choose from
the above two options. Your proposal on that was made, yes... but I find
the 'multi-line string' even better than 'triple-quoted string literal'.

I would love to provide a patch but I don't know how it's made.
msg66654 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2008-05-11 19:22
Stop bothering us.
History
Date User Action Args
2022-04-11 14:56:34adminsetgithub: 47071
2008-05-11 19:22:03gvanrossumsetstatus: open -> closed
resolution: not a bug
messages: + msg66654
2008-05-11 19:17:18chestercreate