[Django] #26031: cache.get_or_set isn't available in 1.8

12 views
Skip to first unread message

Django

unread,
Jan 4, 2016, 3:19:30 AM1/4/16
to django-...@googlegroups.com
#26031: cache.get_or_set isn't available in 1.8
-------------------------------+----------------------------------------
Reporter: gautamk | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Keywords: cache, wrong documentation
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+----------------------------------------
The documentation wrongly suggest that cache.get_or_set is available in
django 1.8,

https://docs.djangoproject.com/en/1.8/topics/cache/#django.core.cache.caches

but when I check the source under the 1.8.8 tag I couldn't find the method
definition.

https://github.com/django/django/blob/1.8.8/django/core/cache/backends/base.py

--
Ticket URL: <https://code.djangoproject.com/ticket/26031>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 4, 2016, 3:21:00 AM1/4/16
to django-...@googlegroups.com
#26031: cache.get_or_set isn't available in 1.8
-------------------------------------+-------------------------------------

Reporter: gautamk | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: cache, wrong- | Triage Stage:
documentation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by gautamk):

* keywords: cache, wrong documentation => cache, wrong-documentation
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0


--
Ticket URL: <https://code.djangoproject.com/ticket/26031#comment:1>

Django

unread,
Jan 4, 2016, 3:21:41 AM1/4/16
to django-...@googlegroups.com
#26031: cache.get_or_set isn't available in 1.8
-------------------------------------+-------------------------------------

Reporter: gautamk | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: cache, wrong- | Triage Stage:
documentation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by gautamk:

Old description:

> The documentation wrongly suggest that cache.get_or_set is available in
> django 1.8,
>
> https://docs.djangoproject.com/en/1.8/topics/cache/#django.core.cache.caches
>
> but when I check the source under the 1.8.8 tag I couldn't find the
> method definition.
>
> https://github.com/django/django/blob/1.8.8/django/core/cache/backends/base.py

New description:

The documentation wrongly suggests that cache.get_or_set is available in
django 1.8,

https://docs.djangoproject.com/en/1.8/topics/cache/#django.core.cache.caches

but when I check the source under the 1.8.8 tag I couldn't find the method
definition.

https://github.com/django/django/blob/1.8.8/django/core/cache/backends/base.py

--

--
Ticket URL: <https://code.djangoproject.com/ticket/26031#comment:2>

Django

unread,
Jan 4, 2016, 6:23:37 AM1/4/16
to django-...@googlegroups.com
#26031: cache.get_or_set isn't available in 1.8
-------------------------------------+-------------------------------------
Reporter: gautamk | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
| worksforme

Keywords: cache, wrong- | Triage Stage:
documentation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):

* status: new => closed
* resolution: => worksforme


Comment:

I don't see a mention of "get_or_set" on the page you linked or in the
"stable/1.8.x" branch.

--
Ticket URL: <https://code.djangoproject.com/ticket/26031#comment:3>

Reply all
Reply to author
Forward
0 new messages