I've had about 5 or 6 of them.
Paul
On Thu, 4 Nov 2021 at 19:22, Brett Cannon wrote:
>
> What notification? (I fully admit I may not have gotten one due to some team
> I'm in, but I have no such notification if it happened recently.)
>
> On Thu, Nov 4, 2021 at 12:16 AM Larry Hastings wrote:
>>
I was looking into migrating twisted trac to github, and contacted GitHub
support who told me there's a secret API that doesn't notify subscribers
https://gist.github.com/jonmagic/5282384165e0f86ef105
On Thu, 4 Nov 2021, 19:28 Brett Cannon, wrote:
> What notification? (I fully admit I may not
On 11/4/21 12:21 PM, Brett Cannon wrote:
> What notification? (I fully admit I may not have gotten one due to some team
I'm in, but I have
> no such notification if it happened recently.)
I've received 20-30 in the last three or four days. I'm not concerned about
it, just providing a data
What notification? (I fully admit I may not have gotten one due to some
team I'm in, but I have no such notification if it happened recently.)
On Thu, Nov 4, 2021 at 12:16 AM Larry Hastings wrote:
>
> I guess this is part of the migration from bpo to GitHub issues? Maybe
> the initial work
On Fri, Nov 5, 2021 at 2:59 AM Jonathan Goble wrote:
>
> On Thu, Nov 4, 2021 at 10:37 AM Eric Fahlgren wrote:
>>
>> On Thu, Nov 4, 2021 at 12:01 AM Ethan Furman wrote:
>>>
>>> >>> bytearray.fromsize(5, fill=b'\x0a')
>>> bytearray(b'\x0a\x0a\x0a\x0a\x0a')
>>
>>
>> What happens if you
On Thu, Nov 4, 2021 at 10:37 AM Eric Fahlgren
wrote:
> On Thu, Nov 4, 2021 at 12:01 AM Ethan Furman wrote:
>
>> >>> bytearray.fromsize(5, fill=b'\x0a')
>> bytearray(b'\x0a\x0a\x0a\x0a\x0a')
>>
>
> What happens if you supply more than one byte for the fill argument?
> Silent
On Thu, Nov 4, 2021 at 12:01 AM Ethan Furman wrote:
> >>> bytearray.fromsize(5, fill=b'\x0a')
> bytearray(b'\x0a\x0a\x0a\x0a\x0a')
>
What happens if you supply more than one byte for the fill argument?
Silent truncation, raise ValueError('too long') or ???
I guess this is part of the migration from bpo to GitHub issues? Maybe
the initial work could be done in a private repo, to cut down on the
spurious email notifications to literally everybody subscribed to
cpython? Which is a lot of people.
//arry/
The final PEP with SC feedback incorporated and one last addition: `bytes.ascii` as a replacement for the Python 2 idiom
of `str(some_var)` to get the bytes version, and the Python 3 workaround of either the correct
`str(some_var).encode('astii') or the potentially wrong
