[Python-Dev] Possible rough edges in Python 3 metaclasses (was Re: Language reference updated for metaclasses) (original) (raw)
PJ Eby pje at telecommunity.com
Wed Jun 6 05:48:35 CEST 2012
- Previous message: [Python-Dev] Possible rough edges in Python 3 metaclasses (was Re: Language reference updated for metaclasses)
- Next message: [Python-Dev] Possible rough edges in Python 3 metaclasses (was Re: Language reference updated for metaclasses)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jun 5, 2012 at 8:14 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
On reflection, I'm actually inclined to agree. The next version of the PEP will propose the addition of type.decorate(). This new method will be invoked after the class is created and the class cell is populated, but before lexical decorators are applied.
Why not have type.call() do the invocation? That is, why does it need to become part of the external class-building protocol?
(One advantage to putting it all in type.call() is that you can emulate the protocol in older Pythons more easily than if it's part of the external class creation dance.) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120605/44cdf202/attachment.html>
- Previous message: [Python-Dev] Possible rough edges in Python 3 metaclasses (was Re: Language reference updated for metaclasses)
- Next message: [Python-Dev] Possible rough edges in Python 3 metaclasses (was Re: Language reference updated for metaclasses)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]