It probably won't fly but why not bytes.frombyte?
There's no such thing as a byte type in Python, only bytes, so I want
to argue it makes it clear the argument is a number in the range
0..255 and the result is a bytes object containing this single byte
value.
Tentatively,
Arnaud
PS. But truly I
On 3 May 2015 at 02:22, Greg Ewing wrote:
> Guido van Rossum wrote:
>>
>> On Sat, May 2, 2015 at 1:18 PM, Arnaud Delobelle > <mailto:arno...@gmail.com>> wrote:
>>
>> Does this mean that
>> somehow "await x" guarantees that the corou
On 3 May 2015 at 16:24, Steven D'Aprano wrote:
> On Fri, May 01, 2015 at 09:24:47PM +0100, Arnaud Delobelle wrote:
>
>> I'm not convinced that allowing an object to be both a normal and an
>> async iterator is a good thing. It could be a recipe for confusion.
>
On 1 May 2015 at 20:59, Guido van Rossum wrote:
> On Fri, May 1, 2015 at 12:49 PM, Ron Adam wrote:
>>
>>
>> Another useful async function might be...
>>
>>async def yielding():
>>pass
>>
>> In a routine is taking very long time, just inserting "await yielding()"
>> in the long calcula
On 1 May 2015 at 20:24, Yury Selivanov wrote:
> On 2015-05-01 3:19 PM, Ethan Furman wrote:
[...]
>> If we must have __aiter__, then we may as well also have __anext__;
>> besides
>> being more consistent, it also allows an object to be both a normol
>> iterator
>> and an asynch iterator.
>
>
> And
On 1 May 2015 at 21:27, Yury Selivanov wrote:
> On 2015-05-01 4:24 PM, Arnaud Delobelle wrote:
>>
>> On 1 May 2015 at 20:24, Yury Selivanov wrote:
>>>
>>> On 2015-05-01 3:19 PM, Ethan Furman wrote:
>>
>> [...]
>>>>
>>>&g
On 29 April 2015 at 20:42, Yury Selivanov wrote:
> Everybody is pulling me in a different direction :)
> Guido proposed to call them "native coroutines". Some people
> think that "async functions" is a better name. Greg loves
> his "cofunction" term.
>
> I'm flexible about how we name 'async def
On 25 April 2015 at 22:02, Yury Selivanov wrote:
[...]
> On 2015-04-25 4:47 PM, Arnaud Delobelle wrote:
[...]
>> 1. About the 'async for' construct. Each iteration will create a new
>> coroutine object (the one returned by Cursor.__anext__()) and it seems
>> to
o a new
feature of Python. I feel that if I was not familiar with yield from
and asyncio I would not be able to understand this PEP, even though
potentially one could use the new constructs without knowing anything
about them.
Cheers,
--
Arnaud Delobelle
[1] https://do
On Tue, 21 Apr 2015 at 09:59 Cory Benfield wrote:
[...]
> Further, Python's type system is not sufficiently flexible to allow
> library authors to adequately specify the types their code actually
> works on. I need to be able to talk about interfaces, because
> interfaces are the contract around
On 2 Mar 2008, at 02:00, Alex Martelli wrote:
> On Sat, Mar 1, 2008 at 11:11 AM, Barry Warsaw <[EMAIL PROTECTED]>
> wrote:
> ...
>>> I also propose translations of the shorter text to important
>>> languages
>>> like French, German, Japanese, Portuguese and Spanish. I'm willing
>>> to
>>>
11 matches
Mail list logo
