#32749: PyMemcacheCache uses default_noreply=False although pymemcache 
recommends
to set to True
-------------------------------------+-------------------------------------
     Reporter:  yakirsudry           |                    Owner:  Nishant
         Type:                       |  Sagar
  Cleanup/optimization               |                   Status:  assigned
    Component:  Documentation        |                  Version:  3.2
     Severity:  Normal               |               Resolution:
     Keywords:  pymemcache           |             Triage Stage:  Accepted
  PyMemcacheCache                    |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Old description:

> I'm not sure why would we do that, since changing to True will slightly
> speed up the usage of the cache

New description:

 I checked the pymemcached documentation and it says  noreply will not read
 errors returned from the memcached server.

 If a function with noreply=True causes an error on the server, it will
 still succeed and your next call which reads a response from memcached may
 fail unexpectedly.

 pymemcached will try to catch and stop you from sending malformed inputs
 to memcached, but if you are having unexplained errors, setting
 noreply=False may help you troubleshoot the issue.

 What do we supposed to  do now?

 PS- I'm new to this project so can anyone give me some suggestion to fix
 this issue

--

Comment (by Nishant Sagar):

 I checked the pymemcached documentation and it says  noreply will not read
 errors returned from the memcached server.

 If a function with noreply=True causes an error on the server, it will
 still succeed and your next call which reads a response from memcached may
 fail unexpectedly.

 pymemcached will try to catch and stop you from sending malformed inputs
 to memcached, but if you are having unexplained errors, setting
 noreply=False may help you troubleshoot the issue.

 What do we supposed to  do now?

 PS- I'm new to this project so can anyone give me some suggestion to fix
 this issue

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.0f250b3722603447f6d88c6b7350ab4f%40djangoproject.com.

Reply via email to