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 josh.r
Recipients Elaphurus, josh.r, larry
Date 2021-04-13.03:56:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618286200.17.0.642193445143.issue43824@roundup.psfhosted.org>
In-reply-to
Content
__deepcopy__ is required to take a second argument by the rules of the copy module; the second argument is supposed to be a memo dictionary, but there's no reason to use it for array.array (it can't contain Python objects, and you only use the memo dictionary when recursing to Python objects you contain).

Sure, the second argument isn't being type-checked, but it's not used at all, and it's only supposed to be invoked indirectly via copy.deepcopy (that passes a dict).

Can you explain what is wrong here that needs to be fixed? Seems like a straightforward "protocol requires argument, but use case doesn't have anything to do with it, so it ignores it". Are you suggesting adding type-checks for something that never gets used?
History
Date User Action Args
2021-04-13 03:56:40josh.rsetrecipients: + josh.r, larry, Elaphurus
2021-04-13 03:56:40josh.rsetmessageid: <1618286200.17.0.642193445143.issue43824@roundup.psfhosted.org>
2021-04-13 03:56:40josh.rlinkissue43824 messages
2021-04-13 03:56:38josh.rcreate