[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-dev
Subject:    [Python-Dev] Please take your time reading PEPs (was: PEP 578: Python Runtime Audit Hooks)
From:       Brett Cannon <brett () python ! org>
Date:       2019-03-29 19:03:48
Message-ID: CAP1=2W5+L0P2cEz8M2A1ZDYM_1_=wL-_Qwn0kF41M=-x2XWA9A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Mar 28, 2019 at 5:03 PM Victor Stinner <vstinner@redhat.com> wrote:

> Hi,
>
> I read quickly the PEP
>

I would like to encourage everyone to read PEPs so that they never feel the
need to write those words ever again. ;)

PEPs are never decided in less than 24 hours, so there is no rush to read a
PEP as quickly as possible in order to reply ASAP. We also have so much
volume as it is when discussing PEPs that I think we should be encouraging
people to take the time to be informed by reading thoroughly before
replying so the back-and-forth is minimized and optimized for impactful
discussions (personally, I would love it if we all aimed for one, thorough
response/day when discussing PEPs, but that's just me). Otherwise we end up
with way more time spent in replies to things that would not have been
necessary to ask if we took our time reading. Remember, every email you
send is read by tons of other people and so there's a real time commitment
you're asking of the world every time you hit that Reply button.

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Mar 28, 2019 at 5:03 PM Victor Stinner &lt;<a \
href="mailto:vstinner@redhat.com">vstinner@redhat.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br> <br>
I read quickly the PEP<br></blockquote><div><br></div><div>I would like to encourage \
everyone to read PEPs so that they never feel the need to write those words ever \
again. ;)</div><div><br></div><div>PEPs are never decided in less than 24 hours, so \
there is no rush to read a PEP as quickly as possible in order to reply ASAP. We also \
have so much volume as it is when discussing PEPs that I think we should be \
encouraging people to take the time to be informed by reading thoroughly before \
replying so the back-and-forth is minimized and optimized for impactful discussions \
(personally, I would love it if we all aimed for one, thorough response/day when \
discussing PEPs, but that&#39;s just me). Otherwise we end up with way more time \
spent in replies to things that would not have been necessary to ask if we took our \
time reading. Remember, every email you send is read by tons of other people and so \
there&#39;s a real time commitment you&#39;re asking of the world every time you hit \
that Reply button.<br></div></div></div>



_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/python-dev-marcsub-zyf4%40marc.info


[prev in list] [next in list] [prev in thread] [next in thread]