Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #18054
| From | Lie Ryan <lie.1296@gmail.com> |
|---|---|
| Subject | Re: Possible bug in string handling (with kludgy work-around) |
| Date | 2011-12-28 08:23 +1100 |
| References | <mailman.4112.1324938867.27778.python-list@python.org> <4ef91afb$0$29973$c3e8da3$5496439d@news.astraweb.com> <mailman.4133.1324997611.27778.python-list@python.org> <cce5eb97-8e7f-48c6-8f0d-ec6442871196@k28g2000yqn.googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.4152.1325021001.27778.python-list@python.org> (permalink) |
On 12/28/2011 05:04 AM, Rick Johnson wrote:
> --
> Note: superfluous indention removed for clarity!
> --
>
> On Dec 27, 8:53 am, Dennis Lee Bieber<wlfr...@ix.netcom.com> wrote:
>> You can get by without the backslash in this situation too, by using
>> triple quoting:
>
> I would not do that because:
> 1. Because Python already has TWO string literal delimiters (' and ")
> 2. Because triple quote string literals are SPECIFICALLY created to
> solve the "multi-line issue"
> 3. Because you can confuse the hell out of someone who is reading
> Python code and they may miss the true purpose of triple quotes in
> Python
>
> But this brings up a very important topic. Why do we even need triple
> quote string literals to span multiple lines? Good question, and one i
> have never really mused on until now. It's amazing how much BS we just
> accept blindly! WE DON'T NEED TRIPLE QUOTE STRINGS! What we need is
> single quote strings that span multiple lines and triple quotes then
> become superfluous! For the problem of embedding quotes in string
> literals, we should be using markup. A SIMPLISTIC MARKUP!
>
> " This is a multi line
> string with a single quote --> <SQ>
> and a double quote --> <DQ>. Here is an
> embedded newline --> <NL>. And a backspace<BS>.
>
> Now we can dispense with all the BS!
> "
Ok, you're trolling.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Possible bug in string handling (with kludgy work-around) Charles Hixson <charleshixsn@earthlink.net> - 2011-12-26 14:23 -0800
Re: Possible bug in string handling (with kludgy work-around) Rick Johnson <rantingrickjohnson@gmail.com> - 2011-12-26 14:48 -0800
Re: Possible bug in string handling (with kludgy work-around) Chris Angelico <rosuav@gmail.com> - 2011-12-27 10:05 +1100
Re: Possible bug in string handling (with kludgy work-around) Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-12-27 01:10 +0000
Re: Possible bug in string handling (with kludgy work-around) Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-12-27 09:53 -0500
Re: Possible bug in string handling (with kludgy work-around) Rick Johnson <rantingrickjohnson@gmail.com> - 2011-12-27 10:04 -0800
Re: Possible bug in string handling (with kludgy work-around) Lie Ryan <lie.1296@gmail.com> - 2011-12-28 08:23 +1100
Re: Possible bug in string handling (with kludgy work-around) Terry Reedy <tjreedy@udel.edu> - 2011-12-27 16:38 -0500
Re: Possible bug in string handling (with kludgy work-around) Rick Johnson <rantingrickjohnson@gmail.com> - 2011-12-27 16:57 -0800
Re: Possible bug in string handling (with kludgy work-around) Lie Ryan <lie.1296@gmail.com> - 2011-12-29 04:54 +1100
Re: Possible bug in string handling (with kludgy work-around) Terry Reedy <tjreedy@udel.edu> - 2011-12-27 16:38 -0500
csiph-web