This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author veky
Recipients Eric Appelt, Mariatta, brett.cannon, docs@python, eric.araujo, rhettinger, veky
Date 2017-09-15.05:40:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
Well, actually, Raymond was proposing an alternative to Py2's special __metaclass__ attribute assignment syntax, which honestly _is_ an abomination (and the big part of reason why that was changed in Py3 to a keyword argument in a class definition).

And Guido missed the point that in frameworks such as Django, the inheritance is the main thing people want, metaclasses just being a technical implementation detail (the easiest proof is that with modern descriptors with __set_name__ and ordered class namespaces, it's unnecessary to use metaclasses in Django model implementation at all). Here it is exactly the opposite.

As I said in the linked comment, I think we missed the opportunity to make Python much more powerful, practically shunning the idea of keyword arguments in a class definition totally. But as it is said, Guido's will  be done. :-) Thanks for the link.
History
Date User Action Args
2017-09-15 05:40:10vekysetrecipients: + veky, brett.cannon, rhettinger, eric.araujo, docs@python, Mariatta, Eric Appelt
2017-09-15 05:40:10vekysetmessageid: <[email protected]>
2017-09-15 05:40:10vekylinkissue30096 messages
2017-09-15 05:40:10vekycreate