Showing content from http://mail.python.org/pipermail/python-dev/attachments/20150817/05cde7ca/attachment.html below:
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/17/2015 03:02 AM, Paul Moore
wrote:<br>
</div>
<blockquote
cite="mid:CACac1F-asVa4WwgReQKmUwkX-eXM2LjnM+94BMfgmaJnzLjFSg@mail.gmail.com"
type="cite">
<pre wrap="">On 17 August 2015 at 05:34, Victor Stinner <a class="moz-txt-link-rfc2396E" href="mailto:victor.stinner@gmail.com"><victor.stinner@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">2015-08-16 7:21 GMT-07:00 Paul Moore <a class="moz-txt-link-rfc2396E" href="mailto:p.f.moore@gmail.com"><p.f.moore@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">3. All of the complex examples look scary, but in practice I wouldn't
write stuff like that - why would anyone do so unless they were being
deliberately obscure?
</pre>
</blockquote>
<pre wrap="">I'm quite sure that users will write complex code in f-strings.
</pre>
</blockquote>
<pre wrap="">So am I. Some people will always write bad code. I won't (or at least,
I'll try not to write code that *I* consider to be complex :-)) but
"you can use this construct to write bad code" isn't an argument for
dropping the feature. If you couldn't find *good* uses, that would be
different, but that doesn't seem to be the case here (at least in my
view).
</pre>
</blockquote>
<br>
I think this corner of the debate is covered by the "Consenting
adults" guiding principle we use 'round these parts.<br>
<br>
Cheers,<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4