[Python-Dev] PEP 3000 and new style classes
holger krekel
hpk at trillke.net
Fri Sep 9 22:30:37 CEST 2005
More information about the Python-Dev mailing list
Fri Sep 9 22:30:37 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 ]
On Fri, Sep 09, 2005 at 11:31 -0700, Russell E. Owen wrote: > In article <20050908211307.GA506 at mithrandi.za.net>, > Tristan Seligmann <mithrandi-python-dev at mithrandi.za.net> wrote: > > > > 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? How would this non-expert have a clue what "from __future__ import new_style_classes" means? holger
- 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