[Python-bugs-list] Missing , not picked up by parser (PR#423)
Tue, 1 Aug 2000 19:11:22 -0400 (EDT)
Sorry, but this is a documented feature: just as in C, adjacent string
literals are concatenated at compile-time. You bumped up against the Dark
Side of that. The Bright Side is, e.g.,
logfile.write("And here I need to write something "
"to a log file that spills over a line "
"of source code but I want it want to "
"appear in the log as one line."
It can't be made an error, as lots of code relies on it now.
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org]On Behalf Of email@example.com
> Sent: Tuesday, August 01, 2000 6:46 PM
> To: firstname.lastname@example.org
> Cc: email@example.com
> Subject: [Python-bugs-list] Missing , not picked up by parser (PR#423)
> Full_Name: Chris Withers
> Version: 1.5.2
> OS: WinNT/Linux
> Submission from: zuul.nipltd.com (188.8.131.52)
> I have something equivalent to this in my code:
> mylist = ['x','y'
> (the real code has much longer contents, hence the line break ;-)
> I think this should throw a parse error 'cos there's a missing comma.
> What actually happens is it ends up as:
> mylist = ['x','yz']
> which is _really_ non-intuitive. I spent a good few hours trying
> to find the
> of an exception in the Squishdot product for Zope until I noticed this.
> I note that:
> mystring = 'x''y'
> is also legal, which I suspect is the roundabout source of this problem.
> Sure that should raise an error and only the following should
> give the result
> that that does:
> mystring = 'x'+'y'
> Python-bugs-list maillist - Pythonfirstname.lastname@example.org