A RetroSearch Logo

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

Search Query:

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

[Python-Dev] PEP 3000 and new style classes

[Python-Dev] PEP 3000 and new style classes [Python-Dev] PEP 3000 and new style classesholger krekel hpk at trillke.net
Fri Sep 9 22:30:37 CEST 2005
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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4