Author rhettinger
Recipients Jelle Zijlstra, r.david.murray, rhettinger, serhiy.storchaka, stutzbach
Date 2018-05-15.23:35:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526427315.52.0.682650639539.issue33519@psf.upfronthosting.co.za>
In-reply-to
Content
> Should we add .copy() to the ABC or remove the promise that all mutable sequences implement .copy()?

The second option would be best.  Let's just clarify that copy() isn't part of the MutableSequence API.

The first option isn't really a choice be it would break existing uses that don't implement copy and because the ABC have a reliable way to create a new instance using the given abstract methods (it has no way of even knowing whether the data is stored locally, in a database, or updated through a REST API, it may not even be possible to reliably create an independent instance).
History
Date User Action Args
2018-05-15 23:35:15rhettingersetrecipients: + rhettinger, stutzbach, r.david.murray, serhiy.storchaka, Jelle Zijlstra
2018-05-15 23:35:15rhettingersetmessageid: <1526427315.52.0.682650639539.issue33519@psf.upfronthosting.co.za>
2018-05-15 23:35:15rhettingerlinkissue33519 messages
2018-05-15 23:35:15rhettingercreate