Tristan Seligmann mithrandi-python-dev at mithrandi.za.net
Thu Sep 8 23:13:07 CEST 2005

• Previous message: [Python-Dev] PEP 3000 and new style classes
• Next message: [Python-Dev] PEP 3000 and new style classes
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

* 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.
-- 
mithrandi, i Ainil en-Balandor, a faer Ambar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mail.python.org/pipermail/python-dev/attachments/20050908/73486fa9/attachment.pgp

---

• Previous message: [Python-Dev] PEP 3000 and new style classes
• Next message: [Python-Dev] PEP 3000 and new style classes
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list