Author barry
Recipients adrien-saladin, barry, berker.peksag, kxroberto, martin.panter, python-dev, r.david.murray, rhettinger
Date 2016-06-13.05:24:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Jun 13, 2016, at 12:09 AM, Martin Panter wrote:

>I think I would support deprecating the __setitem__() etc methods, perhaps
>with a cleanup of the alternatives, e.g. add remove_all(). Also,
>__getitem__() is equivalent to get(), which does not raise KeyError. Although
>according to Issue 12111, David said things are unlikely to change.

I do not support deprecating __setitem__().  I'm okay with developing an
alternative API, but setitem syntax is just too pervasive and convenient.
It's been there since the very earliest days of mimelib (the precursor to the
email package).  If you read and understand the docs, you know exactly what
the semantics are and you know how to use it effectively and safely.
Date User Action Args
2016-06-13 05:24:03barrysetrecipients: + barry, rhettinger, kxroberto, r.david.murray, adrien-saladin, python-dev, berker.peksag, martin.panter
2016-06-13 05:24:02barrylinkissue10839 messages
2016-06-13 05:24:02barrycreate