Author cryvate
Recipients benjamin.peterson, brett.cannon, cryvate, ncoghlan, serhiy.storchaka, yselivanov
Date 2017-11-13.15:19:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510586375.65.0.213398074469.issue32012@psf.upfronthosting.co.za>
In-reply-to
Content
Currently,

    Class C(*some_classes): ...

works 'as expected' and is within grammar and language specification whereas

    Class C(x for x in [object]): ...

does not work but does not cause a syntax error. I can see a use case for both in dynamic class factories. I was going to do this, but was thwarted by another issue (__doc__ cannot be assigned after creation, nor can it be defined as anything but a pure string, any work around or reason that is the case? Not true for e.g. functions).

I think having one of these within the language specification and not the other is odd.
History
Date User Action Args
2017-11-13 15:19:35cryvatesetrecipients: + cryvate, brett.cannon, ncoghlan, benjamin.peterson, serhiy.storchaka, yselivanov
2017-11-13 15:19:35cryvatesetmessageid: <1510586375.65.0.213398074469.issue32012@psf.upfronthosting.co.za>
2017-11-13 15:19:35cryvatelinkissue32012 messages
2017-11-13 15:19:35cryvatecreate