See also 19348 and 8733. https://code.djangoproject.com/ticket/19348 https://code.djangoproject.com/ticket/8733
My opinion hasn't really changed - my experience has been that Kibi and Mebi are prefixes that nobody outside standards organisations give a damn about. In the example you provide (FILE_UPLOAD_MAX_MEMORY_SIZE), the size that is enforced is 2621440; 2.5 MB is given as an indicative size - saying 2.5 MiB might technically be more correct, but doesn't improve clarity of expression in any way, IMHO. And someone actually checking their file system will quite often be using an operating system that reports MB in 1024 blocks - "df -h" under Unix file systems, for example, reports 1013412 kB as 990 MB (tested on Ubuntu 12.04). So us being "more correct" won't actually make it any easier for end users to work out what's going on. So, count me as -0. Russ %-) On Tue, Jan 13, 2015 at 7:53 AM, Markus Holtermann <[email protected] > wrote: > Hey folks, > > I saw that the Django docs currently use file size units kB, MB, etc. > that refer to a multiple of 1000 (1000, 1000000 bytes respectively -- > > https://docs.djangoproject.com/en/dev/ref/settings/#file-upload-max-memory-size > ). But the numbers actually are to the power of 1024. To remedy > inconsistencies there are binary prefixes KiB (Kibibyte), MiB > (Mebibyte), etc. which refer to 1024 and 1048576 bytes respectively ( > http://en.wikipedia.org/wiki/Binary_prefix ) > > The Python documentation itself changed the notation about 2 years ago ( > http://bugs.python.org/issue17193 ) -- Thanks for the hint, Berker. > > I therefore propose to change the notation to use the binary prefix. > > I opened a ticket to track this proposal: > https://code.djangoproject.com/ticket/24140 > > Input and thoughts welcome :) > > /Markus > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/54B45E6B.5080505%40markusholtermann.eu > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849PcrQTw8%3DuVzx0UMmGePx6TGoX9qXiy48sEOB9KJGOdw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
