#32307: Allow change DATA_UPLOAD_MAX_MEMORY_SIZE per view
-------------------------------+--------------------------------------
Reporter: lcd1232 | Owner: nobody
Type: New feature | Status: closed
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Hi. Thanks for the report.
I'm going to initially say `wontfix` here.
This would add a degree of complexity into areas of the framework that are
not generally user accessible, such that I don't think it would be
acceptable.
As a workaround, either up `DATA_UPLOAD_MAX_MEMORY_SIZE` or run a separate
private internal instance exposing the view with the requirement for the
upped limit.
If you'd like to raise the topic on the DevelopersMailingList, you're
welcome to do so (but I'd have a look at how
`DATA_UPLOAD_MAX_MEMORY_SIZE` is used to think how exposing it might be
feasible first.)
--
Ticket URL: <https://code.djangoproject.com/ticket/32307#comment:1>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.fa9aece58c975ba7a06d11911401901e%40djangoproject.com.
