#30669: Can FILE_UPLOAD_MAX_MEMORY_SIZE be set to None?
-------------------------------------+-------------------------------------
Reporter: Lincoln | Owner: nobody
Type: Bug | Status: new
Component: File | Version: master
uploads/storage |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
FILE_UPLOAD_MAX_MEMORY_SIZE, |
None, settings |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Godwin):
I agree that there's no situation it should be None - the "is None"
statement is likely a leftover from my testing and development.
DATA_UPLOAD_MAX_MEMORY_SIZE may well be the right thing to use - I would
appreciate other people's opinion on this one since it's not totally clear
to me how the failure/enforcement modes of those two settings are defined.
--
Ticket URL: <https://code.djangoproject.com/ticket/30669#comment:5>
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/070.ed46cbf611da38a33b8220d8f7607d2e%40djangoproject.com.
