RetroSearch Browse

Sat Oct 14 11:57:59 EDT 2017 · https://mail.python.org/pipermail/python-dev/2017-October/149842.html

On 14 October 2017 at 17:49, Ethan Furman <ethan at stoneleaf.us> 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
several specific examples why we don't want metaclasses to implement
generic class machinery/internals.

Could you please elaborate more what is wrong with PEP 560 and what do you
mean by "class definition protections"

--
Ivan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171014/fbeb35ff/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-October/149842.html below:

[Python-Dev] What is the design purpose of metaclasses vs code generating decorators? (was Re: PEP 557: Data Classes)