Re: PEP 448 review

Brett Cannon <[email protected]> Wed, 29 Mar 2023 13:23:03 -0700
Newsgroups gmane.comp.python.devel
Message-ID <CAP1=2W7=18zjSEZGN-r6zv=QEfNHANNxkUqX36+tVvph+36T1w@mail.gmail.com>
--===============0533662183388736879==
Content-Type: multipart/alternative; boundary="0000000000004bf42805f80fbf4b"

--0000000000004bf42805f80fbf4b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Wow, we are now getting Canadian-specific spam!

Since the volume on this mailing list is so low, should we change everyone
to be moderated to start and then remove that after they have posted
appropriately? Or did this get through by accident?

On Wed, Mar 29, 2023 at 12:19=E2=80=AFPM <[email protected]> wro=
te:

> It seems like you have thoroughly read through the PEP and the discussion
> thread and have formed an opinion about the proposed changes. It's great
> that you have taken the time to understand the proposal and the reasoning
> behind it.
>
> Georg Brandl's comments and Greg Ewing's explanations do shed light on
> some of the concerns raised by the proposal. However, it is good to see
> that you find the sequence and dict flattening syntax proposals to be cle=
an
> and logical.
>
> Regarding the comprehensions part of the proposal, it appears that you ar=
e
> ambivalent about it. You acknowledge that it provides a way to flatten a
> sequence of sequences, but you also point out some of the odd edge cases
> that you discovered while experimenting in the interpreter. It's good to
> see that you are taking a cautious approach and are not rushing to endors=
e
> this part of the proposal.
>
> Overall, your analysis is thoughtful and well-reasoned. It's good to see
> that you are engaging with the proposal in a critical manner and taking
> into account the different perspectives presented in the discussion threa=
d.
> Regards: https://www.extraappliance.ca/washing-machine-repair-edmonton/
> _______________________________________________
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/6BP32=
AXSJAJPWHU274M3RBLLFUBSQUC6/
> Code of Conduct: http://python.org/psf/codeofconduct/
>

--0000000000004bf42805f80fbf4b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Wow, we are now getting Canadian-specific spam!</div>=
<div><br></div><div>Since the volume on this mailing list is so low, should=
 we change everyone to be moderated to start and then remove that after the=
y have posted appropriately? Or did this get through by accident?<br></div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Wed, Mar 29, 2023 at 12:19=E2=80=AFPM &lt;<a href=3D"mailto:extraapplian=
[email protected]">[email protected]</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">It seems like you have thorou=
ghly read through the PEP and the discussion thread and have formed an opin=
ion about the proposed changes. It&#39;s great that you have taken the time=
 to understand the proposal and the reasoning behind it.<br>
<br>
Georg Brandl&#39;s comments and Greg Ewing&#39;s explanations do shed light=
 on some of the concerns raised by the proposal. However, it is good to see=
 that you find the sequence and dict flattening syntax proposals to be clea=
n and logical.<br>
<br>
Regarding the comprehensions part of the proposal, it appears that you are =
ambivalent about it. You acknowledge that it provides a way to flatten a se=
quence of sequences, but you also point out some of the odd edge cases that=
 you discovered while experimenting in the interpreter. It&#39;s good to se=
e that you are taking a cautious approach and are not rushing to endorse th=
is part of the proposal.<br>
<br>
Overall, your analysis is thoughtful and well-reasoned. It&#39;s good to se=
e that you are engaging with the proposal in a critical manner and taking i=
nto account the different perspectives presented in the discussion thread.<=
br>
Regards: <a href=3D"https://www.extraappliance.ca/washing-machine-repair-ed=
monton/" rel=3D"noreferrer" target=3D"_blank">https://www.extraappliance.ca=
/washing-machine-repair-edmonton/</a><br>
_______________________________________________<br>
Python-Dev mailing list -- <a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]=
rg" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://mail.python.org/mailman3/lists/python-dev.python.org/" r=
el=3D"noreferrer" target=3D"_blank">https://mail.python.org/mailman3/lists/=
python-dev.python.org/</a><br>
Message archived at <a href=3D"https://mail.python.org/archives/list/python=
[email protected]/message/6BP32AXSJAJPWHU274M3RBLLFUBSQUC6/" rel=3D"noreferre=
r" target=3D"_blank">https://mail.python.org/archives/list/python-dev@pytho=
n.org/message/6BP32AXSJAJPWHU274M3RBLLFUBSQUC6/</a><br>
Code of Conduct: <a href=3D"http://python.org/psf/codeofconduct/" rel=3D"no=
referrer" target=3D"_blank">http://python.org/psf/codeofconduct/</a><br>
</blockquote></div>

--0000000000004bf42805f80fbf4b--

--===============0533662183388736879==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline