In article <[EMAIL PROTECTED]>, Tristan Seligmann <[EMAIL PROTECTED]> wrote:
> * Lisandro Dalcin <[EMAIL PROTECTED]> [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 _______________________________________________ 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
