#35604: Unexpected behaviour of FileSystemStorage.exists() due to latest changes
--------------------------------------+------------------------------------
Reporter: Stefan Hammer | Owner: (none)
Type: Bug | Status: new
Component: File uploads/storage | Version: 5.1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Sarah Boyce):
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
* type: Uncategorized => Bug
Comment:
[https://github.com/jschneier/django-
storages/issues/1430#issuecomment-2230281809 Comment on the issue in
django-storages]
Given the engagement on the discussion around what .exists() should do in
the overwrite case, and the recent security patch to Django, it makes
sense for FileSystemStorage to also overwrite `get_available_name()` but
leave the existing exists behaviour. This previously was not something we
could endorse.
A clarification to the `FileSystemStorage` docs also make sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/35604#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070190ba98fe74-aeedb189-7a27-4bb0-85af-c008bc6ed62e-000000%40eu-central-1.amazonses.com.
