On Tue, Aug 9, 2016 at 12:29 AM Guido van Rossum wrote:
> On Mon, Aug 8, 2016 at 2:11 PM, אלעזר wrote:
>
>> Feels like named parameters are better off being an OrderedDict in the
>> first place.
>>
>
> PEP 468.
>
>
Sorry, I should have read this PEP before.
> NamedTuple pushes OrderedDict to b
On Mon, Aug 8, 2016 at 3:08 PM, אלעזר wrote:
> On Tue, Aug 9, 2016 at 12:29 AM Guido van Rossum wrote:
>
>> On Mon, Aug 8, 2016 at 2:11 PM, אלעזר wrote:
>>
>>> Feels like named parameters are better off being an OrderedDict in the
>>> first place.
>>>
>>
>> PEP 468.
>>
>>
> Sorry, I should have
On 08.08.2016 19:06, Yury Selivanov wrote:
You have to be aware of what you're decorating. Always.
You have to be aware of what the decorator does first before you decide
if it's relevant to be aware of what you're decorating.
For instance, here's an example of a buggy code:
@functools.lru
On 9 August 2016 at 08:37, Sven R. Kunze wrote:
> From what I've heard in the wild, that most if not all pieces of async are
> mirroring existing Python features. So, building async basically builds a
> parallel structure in Python resembling Python. Async generators complete
> the picture. Some
Just don't oversell run_until_complete() -- some people coming from
slightly different event loop paradigms expect to be able to pump for
events at any point, possibly causing recursive invocations. That doesn't
work here (and it's a feature it doesn't).
On Mon, Aug 8, 2016 at 8:23 PM, Nick Coghla
אלעזר wrote:
class Starship(tuple):
damage: int = 0
captain: str = "Kirk"
Is an obvious syntax for
Starship = NamedTuple('Starship', [('damage', int), ('captain', str)])
But the untyped version of that already has a meaning --
it's a tuple subclass with two extra class attri
