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 bolorsociedad, rhettinger, vstinner
Date 2018-11-24.01:16:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543022205.18.0.788709270274.issue35300@psf.upfronthosting.co.za>
In-reply-to
Content
I concur with Victor.  The proposed API change defeats the purpose of the cache.  By design, the intent of the cache is to reuse the previously computed value.

I can add something like this to the docs: """In general, the LRU cache should only be used when you want to reuse previously computed values.  Accordingly, it doesn't make sense to cache functions with side-effects, functions that need to create distinct mutable objects on each call, or impure functions such as time() or random()."""
History
Date User Action Args
2018-11-24 01:16:45rhettingersetrecipients: + rhettinger, vstinner, bolorsociedad
2018-11-24 01:16:45rhettingersetmessageid: <1543022205.18.0.788709270274.issue35300@psf.upfronthosting.co.za>
2018-11-24 01:16:45rhettingerlinkissue35300 messages
2018-11-24 01:16:43rhettingercreate