Greg Ewing <[EMAIL PROTECTED]> wrote: >> "from __future__ import new_classes" exists, but the syntax is >> different: >> >> __metaclass__ = type > > Although it's not a very obvious spelling, > particularly to the casual reader who may not be > familiar with the intricacies of classes and > metaclasses. I don't think it would hurt to have > it available as a __future__ import as well. > > There's also the advantage that all of a > module's future assumptions could then be > documented uniformly in one place, i.e. in > a __future__ import at the top.
+1. Giovanni Bajo _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
