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.

Author aklish
Recipients aklish
Date 2014-10-28.18:04:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414519480.06.0.561674688361.issue22754@psf.upfronthosting.co.za>
In-reply-to
Content
Implicit string literal concatenation where
"string1" "string2"
becomes
"string1string2"
should be a language syntax error - not a feature.

This creates a silent error whenever someone builds a list of strings and forgets a comma.

I can't think of any good reason why the language supports this.  There are easier ways to build multi-line strings and there are already two explicit ways to do this on a single line.

It also violates the python principle:
"There should be one— and preferably only one —obvious way to do it"

I realize changing this might break someone's code.  If that is a large concern, maybe the interpreter could support an option to enable/disable support for this.
History
Date User Action Args
2014-10-28 18:04:40aklishsetrecipients: + aklish
2014-10-28 18:04:40aklishsetmessageid: <1414519480.06.0.561674688361.issue22754@psf.upfronthosting.co.za>
2014-10-28 18:04:39aklishlinkissue22754 messages
2014-10-28 18:04:39aklishcreate