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 levkivskyi
Recipients eric.smith, gvanrossum, levkivskyi
Date 2018-03-22.14:14:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521728066.58.0.467229070634.issue32505@psf.upfronthosting.co.za>
In-reply-to
Content
> you'll notice that's an error?

Yes, but there are other scenarios, like using `init=False` or updating existing class definition and forgetting to update call sites (which will still work), etc.

What would we lose by not flagging this as an error? I think there are no legitimate use cases for such code, and implementation is straightforward. If you don't have time I can do this myself.
History
Date User Action Args
2018-03-22 14:14:26levkivskyisetrecipients: + levkivskyi, gvanrossum, eric.smith
2018-03-22 14:14:26levkivskyisetmessageid: <1521728066.58.0.467229070634.issue32505@psf.upfronthosting.co.za>
2018-03-22 14:14:26levkivskyilinkissue32505 messages
2018-03-22 14:14:26levkivskyicreate