➜

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 serhiy.storchaka
Recipients jaraco, rhettinger, serhiy.storchaka
Date 2015-10-23.08:05:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445587515.83.0.974709582893.issue25447@psf.upfronthosting.co.za>
In-reply-to
Content 
Using lru_cache() is an implementation detail. I think that lru_cache wrapper should be perfect wrapper, it should support all protocols that are supported by wrapped function (at the same extent as original Python implementation).

Proposed simple patch adds support for pickling, copying and deep-copying lru_cache wrappers. lru_cache wrapper is serialized as global object, i.e. deepcopy() returns the same object, as was in 3.4. Implementing true deep copying (with any semantic) is not so easy, especially for Python implementation.
History
Date User Action Args
2015-10-23 08:05:15serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, jaraco
2015-10-23 08:05:15serhiy.storchakasetmessageid: <1445587515.83.0.974709582893.issue25447@psf.upfronthosting.co.za>
2015-10-23 08:05:15serhiy.storchakalinkissue25447 messages
2015-10-23 08:05:15serhiy.storchakacreate