RetroSearch Browse

Fri Sep 9 20:31:47 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-September/056335.html

In article <20050908211307.GA506 at mithrandi.za.net>,
 Tristan Seligmann <mithrandi-python-dev at mithrandi.za.net> wrote:

> * Lisandro Dalcin <dalcinl at gmail.com> [2005-09-08 13:56:07 -0300]:
> 
> > Yes, you are right. But this way, you are making explicit a behavior
> > that will be implicit in the future.
> > 
> > For example, we could also do:
> > 
> >     two = float(4)/float(2)
> > 
> > instead of 
> > 
> >     from   future   import division
> >     two = 4/2
> 
> Why does it matter if the single statement you insert is spelled
> "  metaclass   = type" instead of "from   future   import whatever"?
> Remember, unlike the division example, you would only have to insert one
> statement, as opposed to changing every use of integer division.

It matters because "metaclass = type" is completely obscure. How would 
any non-expert have a clue what it means?

-- Russell

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

Showing content from https://mail.python.org/pipermail/python-dev/2005-September/056335.html below:

[Python-Dev] PEP 3000 and new style classes