RetroSearch Browse

Fri Jul 14 11:06:17 CEST 2006 · http://mail.python.org/pipermail/python-dev/2006-July/067417.html

Greg Ewing <greg.ewing at canterbury.ac.nz> 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

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

Showing content from http://mail.python.org/pipermail/python-dev/2006-July/067417.html below:

[Python-Dev] Community buildbots