It seems to be an omission in the implementation. Feel free to create a
Trac ticket and offer a patch if you can.
For future reference, please don't cross post between django-users
(appropriate place for "is it a bug?" questions) and django-developers.
Thanks!
On Tuesday, December 1, 2015 at 7:10:57 AM UTC-5, Oleksiy Ivanenko wrote:
>
> Hi,
>
> I'm trying to use Django 1.9rc2.
> But I have issue while using django.core.cahe.cache.get_or_set with
> *DummyCache
> backend*.
>
> from django.core.cache import cache
>
> cache.get_or_set('some_key', 'my_val') # Always return None, instead of
> default value
>
> This behaviour brakes lots of my tests.
>
> Is this behaviour expected? Or we need to figure out some fixes for
> DummyCache backend?
>
>
> ---
> Regards,
> Oleksiy Ivanenko
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/8cc95c4b-520e-49c6-915d-02b96b78d430%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
