Raymond Hettinger added the comment: > 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. ---------- assignee: rhettinger -> serhiy.storchaka priority: high -> normal _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25447> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
