Opinion: Adding a lazy consensus thread will not hurt and I think it
should happen - for the record and for people who might be busy.
I think it's easy to miss the fact that a decision was made in a [DISCUSS]
thread. That's the main purpose of the subject prefixes - to drag attention
for people who are busy and do not read all the emails [VOTE] and [LAZY
CONSENSUS] would surely drag attention.
This was - I think - one of the reasons we had a bit of difficulty/
communication issue when I raised the PRs for ("__future__. annotations") -
it seemed we had consensus but it was all in the [DISCUSS] thread and it
was missed by some people who do not spend a lot of time following all the
discussions happening in the devils (and are not able to parse all the
answers in the long thread to understand that consensus was reached there).
The problem with [LAZY CONSENSUS] is that people answer it with +1 which -
by definition - they should not if they are ok with it :). But that's a
completely different story :)
J.
On Wed, Sep 21, 2022 at 6:35 PM Kaxil Naik <[email protected]> wrote:
> +1 for string normalization.
>
> I love double quoted strings anyways :)
>
> On Wed, 21 Sep 2022 at 16:46, Daniel Standish
> <[email protected]> wrote:
>
>> OK seems like all are in favor. Do we even need a vote? I guess lazy
>> consensus still applies even when you don't formally call for a lazy
>> consensus vote. So I reckon I won't bother.
>>
>> But the implementation.... to @Jed Cunningham <[email protected]>'s
>> point we can wait until closer to 2.5. And I'll connect with folks on
>> slack on other details. But the main decision, to remove `
>> --skip-string-normalization` or not (which is the main question here)
>> seems resolved.
>>
>> Thanks
>>
>
