#26562: Introduce Storage and FileSystemStorage alternate save behaviour
-------------------------------------+-------------------------------------
Reporter: freshquiz | Owner: nobody
Type: New feature | Status: new
Component: File | Version: master
uploads/storage |
Severity: Normal | Resolution:
Keywords: file FileField | Triage Stage: Accepted
storage overwrite filepath |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Ah, indeed, my proposal wouldn't solve the "change the behavior of
Storage.get_available_name()" part of the problem.
Perhaps we can make a backwards-incompatible change there and move the
"try to find an available name" logic in a mixin? This would make it
reasonably easy for projets that extend `Storage` and depend on that logic
to keep it.
--
Ticket URL: <https://code.djangoproject.com/ticket/26562#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1cd5d82dd16bbc5413f26ce874b972e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
