On Sep 14, 2020, at 01:07, Cameron Simpson wrote:
> On 13Sep2020 20:51, Guido van Rossum wrote:
>> On Sun, Sep 13, 2020 at 8:12 PM Cameron Simpson wrote:
>>> As a concrete example, for __length_hint__ and operator.length_hint,
>>> I
>>> wish that in addition to saying "New in version 3.4", it a
On 13Sep2020 20:51, Guido van Rossum wrote:
>On Sun, Sep 13, 2020 at 8:12 PM Cameron Simpson wrote:
>> As a concrete example, for __length_hint__ and operator.length_hint,
>> I
>> wish that in addition to saying "New in version 3.4", it also said
>> "specified by PEP424 [link]", since I had to g
On Sun, Sep 13, 2020 at 8:12 PM Cameron Simpson wrote:
> So, today I noticed __length_hint__, and then operator.length_hint.
> Neither mentions its design purpose, only its specification. And while
> that is minimally enough, knowing the purpoe (size estimation for use by
> presized allocation op
So, today I noticed __length_hint__, and then operator.length_hint.
Neither mentions its design purpose, only its specification. And while
that is minimally enough, knowing the purpoe (size estimation for use by
presized allocation operations) lets an implementor write something more
appropria
Dear Amna, thank you for your interest in my talk, and sorry for the late
reply. Unfortunately, I won't be able to make it this year. Please feel
free to reach out again in the future. Wishing you all the best, and thank
you for organizing this conference :) Claudio
On Thu, 6 Aug 2020 at 18:22, Am
