#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 freshquiz):
Personally, I see the storage API as too coupled to traditional file
systems and (along with the `FileField` implementation) as too protective
in an undesirable and unpreditable way.
#26058 is step in the right direction (along with this ticket) in my
opinion, but I can see how the storage API and `FileField` have backed you
into a backwards compatibility corner.
I only opened this ticket for the sake of all current and future Django
clients, not because I can't achieve the desired behaviour myself.
--
Ticket URL: <https://code.djangoproject.com/ticket/26562#comment:9>
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.1e84227d4cdc8f5fe6201a1957b8e2cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
