Peter Bengtsson
Peter Bengtsson
Can't you just leave it instead? I.e. if you do: ``` >>> from django.core.cache import cache >>> cache.set('foo', 'bar') ``` it will apply whatever's in `django.conf.settings.CACHES["default"]`.
Oh I see. I think you can just use: ``` >>> from django.core.cache import cache >>> cache.set('foo', 'bar', timeout=object()) ``` is the exact same as not specifying it.
I can't merge this because the CI tests aren't running. Any idea why?
Let's see if this restarts the CI tests.
Can you merge in the latest upstream `master` into your branch and push. Perhaps that'll pick up the new GitHub Actions checks.
Let's try if close and re-opening triggers the CI tests.
What the heck?! I don't know why the tests aren't running. I'll have to take a look some day when I have time.
@KarimTayie can you merge in `master` into your branch and push that that should hopefully fix your tests.
Have you tried this locally? Have you tried running the tests for it?
It's actually correct. Its design is just questionable. If you expand it you'll see that the last comment was by Andreea.  What's causing the confusion...