Opened 9 years ago

Closed 9 years ago

#7653 closed (wontfix)

The documentation should be more explicit about file upload sizes

Reported by: Julien Phalip Owned by: nobody
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


I presume all Django users don't necessarily know that 2.5 MB is equal to 2621440 bytes. There should be a newbie-friendly explanation on how to to set the FILE_UPLOAD_MAX_MEMORY_SIZE setting.

Attachments (1)

upload_doc.diff (908 bytes) - added by Julien Phalip 9 years ago.

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by Julien Phalip

Attachment: upload_doc.diff added

comment:1 Changed 9 years ago by Josh Rosen

Has patch: set

comment:2 Changed 9 years ago by Sung-jin Hong

Triage Stage: UnreviewedReady for checkin

comment:3 Changed 9 years ago by Malcolm Tredinnick

Resolution: wontfix
Status: newclosed

It doesn't matter if the reader knows how big 2.5MB is in the end. They either leave the setting alone or set it to a number that is appropriate for that system (and if they're doing the latter, they must know how to measure). Django's documentation assumes you know how to program in Python and edit text files. Assuming you know how to use Google in the unlikely event you don't know what a megabyte is would also be a reasonable assumption.

This patch isn't bad, except it adds a whole paragraph that makes something look important when it's really very, very trivial. So it detracts from the surrounding, more important, information.

Note: See TracTickets for help on using tickets.
Back to Top