Message 253366 - Python tracker

➜

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	rhettinger
Recipients	jaraco, rhettinger, serhiy.storchaka
Date	2015-10-23.05:18:01
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1445577482.38.0.906805078791.issue25447@psf.upfronthosting.co.za>
In-reply-to

Content
> Although it was apparently an artifact of previous > implementations that the cache happened to be deep-copyable, > I hope this expectation can be restored with minimal fuss. Hmm, I'm surprised that a deepcopy ever worked. The LRU cache certainly wasn't designed for that. If Serhiy has a straight-forward way of restoring the behavior (and adding a test for it), that would be reasonable for 3.5.1. However, if it involves twisting the code into knots or risking breakage, it would be better to either close this as "won't fix" or reclassify as a feature request for 3.6.

> Although it was apparently an artifact of previous 
> implementations that the cache happened to be deep-copyable, 
> I hope this expectation can be restored with minimal fuss.

Hmm, I'm surprised that a deepcopy ever worked.  The LRU cache certainly wasn't designed for that.

If Serhiy has a straight-forward way of restoring the behavior (and adding a test for it), that would be reasonable for 3.5.1.  However, if it involves twisting the code into knots or risking breakage, it would be better to either close this as "won't fix" or reclassify as a feature request for 3.6.

History
Date	User	Action	Args
2015-10-23 05:18:02	rhettinger	set	recipients: + rhettinger, jaraco, serhiy.storchaka
2015-10-23 05:18:02	rhettinger	set	messageid: <1445577482.38.0.906805078791.issue25447@psf.upfronthosting.co.za>
2015-10-23 05:18:02	rhettinger	link	issue25447 messages
2015-10-23 05:18:01	rhettinger	create