Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional keyword to forcibly bypass cache #47

Open
safijari opened this issue Nov 10, 2017 · 1 comment
Open

Optional keyword to forcibly bypass cache #47

safijari opened this issue Nov 10, 2017 · 1 comment

Comments

@safijari
Copy link

So, in case I'm not understanding things correctly, is there a way to handle the following use case: I have a function which I need to cache most of the time, but in a few very specific cases I need it run its course. The function is grabbing things from a web api, most of these do not change but some do, and that fact only matters in one use case. Can I provide an additional keyword just for that specific use case?

e.g.

get_data(dont_cache=True)

I'm thinking the best place to implement this (in case this doesn't already exist) would be here. Thoughts?

@szaydel
Copy link
Contributor

szaydel commented Nov 10, 2017

So if you already know that data will be different, is it not better to expire that data in cache? Or am I missing the use-case entirely?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants