On 10/14/2017 11:30 AM, Ivan Levkivskyi wrote:
As a side note, I don't think elimination of metaclasses should be a "goal by
itself".
This is a powerful and flexible mechanism, but there are specific situations
where
metaclasses don't work well because of e.g. frequent conflicts or performance
On 14 October 2017 at 18:14, Ethan Furman wrote:
> On 10/14/2017 08:57 AM, Ivan Levkivskyi wrote:
>
>>
>> Could you please elaborate more what is wrong with PEP 560 and what do
>> you mean by "class definition protections"
>>
>
> Nothing is wrong with PEP 560. What I am referring to is:
>
[snip]
On 15 October 2017 at 02:14, Ethan Furman wrote:
> On 10/14/2017 08:57 AM, Ivan Levkivskyi wrote:
>
>> On 14 October 2017 at 17:49, Ethan Furman wrote:
>>
>
> The problem with PEP 560 is that it doesn't allow the class definition
>>>
>> >> protections that a metaclass does.
>
>>
>> Since the disc
On 10/14/2017 08:57 AM, Ivan Levkivskyi wrote:
On 14 October 2017 at 17:49, Ethan Furman wrote:
The problem with PEP 560 is that it doesn't allow the class definition
>> protections that a metaclass does.
Since the discussion turned to PEP 560, I can say that I don't want this
> to be a ge
On 14 October 2017 at 17:49, Ethan Furman wrote:
> The problem with PEP 560 is that it doesn't allow the class definition
> protections that a metaclass does.
>
Since the discussion turned to PEP 560, I can say that I don't want this to
be a general mechanism, the PEP rationale section gives
sev
On 10/14/2017 07:37 AM, Martin Teichmann wrote:
Things that will not work if Enum does not have a metaclass:
list(EnumClass) -> list of enum members
dir(EnumClass) -> custom list of "interesting" items
len(EnumClass) -> number of members
member in EnumClass -> True or False
- protection from
On 15 October 2017 at 01:00, Martin Teichmann
wrote:
> While I am not worried about the poor computers having to do a lot of
> work creating a throwaway class, I do see the problem with the new
> super. What I would like to see is something like the @wraps decorator
> for classes, such that you c
>> I do worry that things like your autoslots decorator example might be
>> problematic because they create a new class, throwing away a lot of work
>> that was already done. But perhaps the right way to address this would be
>> to move the decision about the instance layout to a later phase? (Not
> Things that will not work if Enum does not have a metaclass:
>
> list(EnumClass) -> list of enum members
> dir(EnumClass) -> custom list of "interesting" items
> len(EnumClass) -> number of members
> member in EnumClass -> True or False
>
> - protection from adding, deleting, and changing membe
