Re: [Django] #36298: file_move_safe with allow_overwrite=True does not truncate previous file when there is an OSError error on rename (was: file_move_safe with allow_overwrite=True does not truncate previous file when there is a permission error on rename)

2 views
Skip to first unread message

Django

unread,
Apr 4, 2025, 3:56:28 AM4/4/25
to django-...@googlegroups.com
#36298: file_move_safe with allow_overwrite=True does not truncate previous file
when there is an OSError error on rename
-------------------------------------+-------------------------------------
Reporter: Sarah Boyce | Owner: Sarah
| Boyce
Type: Bug | Status: assigned
Component: File | Version: 5.2
uploads/storage |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

* summary:
file_move_safe with allow_overwrite=True does not truncate previous
file when there is a permission error on rename
=>
file_move_safe with allow_overwrite=True does not truncate previous
file when there is an OSError error on rename

--
Ticket URL: <https://code.djangoproject.com/ticket/36298#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Reply all
Reply to author
Forward
0 new messages