Bug 2252960 - Handle correctly 'NO FOUND' in memached delete method
Summary: Handle correctly 'NO FOUND' in memached delete method
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-django3
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-05 12:50 UTC by Zhechka TOTEVA
Modified: 2023-12-05 12:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)
patch that fixes the bug (721 bytes, patch)
2023-12-05 12:50 UTC, Zhechka TOTEVA 		no flags Details | Diff
View All

Description Zhechka TOTEVA 2023-12-05 12:50:45 UTC 
Created attachment 2002824 [details]
patch that fixes the bug

Description of problem:


Version-Release number of selected component (if applicable):
python3-django3-3.2.20-1.el8.noarch

How reproducible:
    
With python-memcached 1.58.8 present in EPEL8 if a non-existing key
is attempted for deletion it raises an error

```
File "/usr/lib/python3.6/site-packages/memcache.py", line 584, in _deletetouch
   % (cmd, ' or '.join(expected), line))
```


Actual results:


Expected results:


Additional info:
The fix is attached. The bug officially was fixed in 4.1, by commit https://github.com/django/django/commit/05f3a6186efefc9fca2204a745b992501c6fd91f

Cheers
Zhechka
Note You need to log in before you can comment on or make changes to this bug.