#35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used
-------------------------------------+-------------------------------------
Reporter: bcail | Owner: bcail
Type: Bug | Status: closed
Component: File | Version: dev
uploads/storage |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"8d6a20b656ff3fa18e36954668a44a831c2f6ddd" 8d6a20b]:
{{{#!CommitTicketReference repository=""
revision="8d6a20b656ff3fa18e36954668a44a831c2f6ddd"
Fixed #35604, Refs #35326 -- Made FileSystemStorage.exists() behaviour
independent from allow_overwrite.
Partially reverts 0b33a3abc2ca7d68a24f6d0772bc2b9fa603744e.
Storage.exists(name) was documented to "return False if
the name is available for a new file." but return True if
the file exists. This is ambiguous in the overwrite file
case. It will now always return whether the file exists.
Thank you to Natalia Bidart and Josh Schneier for the
review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35326#comment:16>
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/01070190e4cf62f4-fc5fa232-5fcf-425b-91db-390780077370-000000%40eu-central-1.amazonses.com.
