As the author of `recordclass` I would like to shed some light...
Recorclass originated as a response to the
[question](https://stackoverflow.com/questions/29290359/existence-of-mutable-named-tuple-in-python/29419745#29419745)
on stackoverflow.
`Recordclass` was conceived and implemented as a
Hi,
then intention of my first mail was to start a discussion about this
topic about the pros and cons and possible alternatives.
As long as it is not clear that recordclass or something like that is
accepted to be implemented to the collections module
I do not want to spend any effort on this
On Sunday, September 2, 2018, Zaur Shibzukhov wrote:
>
>
> ---
> *Zaur Shibzukhov*
>
>
> 2018-09-02 22:11 GMT+03:00 Wes Turner :
>
>> Does the value of __hash__ change when attributes of a recordclass change?
>>
>
> Currently recordclass's __hash__ didn't implemented.
>
https://docs.python.org/3
Zaur Shibzukhov wrote:
> `Recordclass` is defined on top of` memoryslots` just like `namedtuple`
> above` tuple`. Attributes are accessed via a descriptor (`itemgetset`),
> which supports both` __get__` and `__set__` by the element index.
>
> As a result, `recordclass` takes up as much memory as`
On Sun, Sep 02, 2018 at 10:56:50PM +0200, Martin Bammer wrote:
> Compared to dataclass:
> dataclass wins only on the topic object size. When it comes to speed and
> functionality (indexing, sorting) dataclass would be my last choice.
I see no sign that recordclass supports sorting. (But I admit
wrote a quick article here :
https://www.pythonmembers.club/2018/09/03/how-to-create-your-own-dsldomain-specific-language-in-python/
--
Abdur-Rahmaan Janhangeer
https://github.com/abdur-rahmaanj
Mauritius
___
Python-ideas mailing list
Python-ideas@pytho
