Ticket https://code.djangoproject.com/ticket/19447 was resolved as wont fix.
Although this PR is insufficient for our needs (we would also need localized abbreviations), it would certainly be more useful than the nothing that exists now. How does the Django team know how many developers would use a feature like this when said developers never get a chance to use it? Django includes a lot of inane features that many fewer developers would use compared to this. The documentation for all of Django is already pretty bad (it's poorly organized, poorly hyperlinked, uses bad examples, etc, regardless of what others say); blocking a PR from acceptance because the documentation doesn't measure up to the bar set in practice is illogical. Practically every site that prints numbers to the screen (read: all sites) could benefit from features like this. If the work is incomplete, let someone take over or explain what else needs to be implemented before acceptance is gained. Closing it as won't fix is irrational and discourages the community (and adoption of the framework). -Charlie PS: I can't add this as a comment to the ticket because: <https://lh3.googleusercontent.com/-rUzIzGN__wM/V5fHwbr3umI/AAAAAAAABt8/jxYrcFrzKKsA0sN9Ex5mnkT1vQSuBeIpwCLcB/s1600/trac.png> -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/163e3b24-aa17-4f82-bc48-3104d3e0d203%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
