On Sun, 10 Feb 2013 22:32:50 +1000 Nick Coghlan <ncoghlan at gmail.com> wrote: > > Replaces many use cases for dynamic setting of ``__metaclass__`` > ----------------------------------------------------------------- > > For use cases that don't involve completely replacing the defined class, > Python 2 code that dynamically set ``__metaclass__`` can now dynamically > set ``__init_class__`` instead. For more advanced use cases, introduction of > an explicit metaclass (possibly made available as a required base class) will > still be necessary in order to support Python 3. So, what are the use cases? I probably write metaclasses once a year, I wonder how much incentive there is to bring an additional complication to the already complicated class construction process. Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4