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 eric.smith
Recipients barry, eric.smith, gvanrossum
Date 2018-05-16.16:02:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526486562.75.0.682650639539.issue33539@psf.upfronthosting.co.za>
In-reply-to
Content
The behavior used to be that we'd raise an error if you tried to overwrite a dunder method. Then we decided that the existence of a dunder method meant you didn't want it overwritten, so now we don't need to explicitly set a flag to False in that case.

However, we did not go back and see which of the flags still make sense. I can't think of a reason why anyone would use the `init` parameter to @dataclass.

It's a little late in the 3.7 release cycle to remove it, so maybe we can decide to deprecate it in 3.8? Although if there's clearly no reason for it to exist, I could be talked in to removing it.

We should probably go through every flag and decide about it individually.
History
Date User Action Args
2018-05-16 16:02:42eric.smithsetrecipients: + eric.smith, gvanrossum, barry
2018-05-16 16:02:42eric.smithsetmessageid: <1526486562.75.0.682650639539.issue33539@psf.upfronthosting.co.za>
2018-05-16 16:02:42eric.smithlinkissue33539 messages
2018-05-16 16:02:42eric.smithcreate