➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author daniel.urban
Recipients amaury.forgeotdarc, benjamin.peterson, daniel.urban, georg.brandl, gvanrossum, ncoghlan, pwerneck, rodsenra, terry.reedy
Date 2011-04-20.19:26:38
SpamBayes Score 0.0014588609
Marked as misclassified No
Message-id <1303327598.83.0.887294701404.issue1294232@psf.upfronthosting.co.za>
In-reply-to
Content 
That may be, but with my latest patch, this works (func is a function):

class X(metaclass=func):
    pass

But this blows up with a TypeError:

class X(object, metaclass=func):
    pass

Is this the desired behaviour? Or should we disallow non-class metaclasses in every case? (And what about backwards-compatibility?)
History
Date User Action Args
2011-04-20 19:26:38daniel.urbansetrecipients: + daniel.urban, gvanrossum, georg.brandl, terry.reedy, amaury.forgeotdarc, ncoghlan, rodsenra, pwerneck, benjamin.peterson
2011-04-20 19:26:38daniel.urbansetmessageid: <1303327598.83.0.887294701404.issue1294232@psf.upfronthosting.co.za>
2011-04-20 19:26:38daniel.urbanlinkissue1294232 messages
2011-04-20 19:26:38daniel.urbancreate