Agreed, this does not belong on core. In particular the formatting of a
duration varies widely depending on the expected age range, languages and
site context. Naturaltime is one implementation, the specific case you seem
to be hinting at is a count of years, which is definitely too particular
for Django inclusion. would make a perfect third party app though!
Mar
On 10 Nov 2015 2:57 am, "Dheerendra Rathor" <dheeru.ratho...@gmail.com>
wrote:
> If we ever need to implement age filter, I would rather suggest for
> modification of naturaltime in django.contrib.humanize to take an optional
> parameter (age = True).
>
> On Tue, 10 Nov 2015 at 01:22 Tim Graham <timogra...@gmail.com> wrote:
>
>> For questions of whether or not to include something like this in core,
>> my own rule of thumb is, "Is this difficult to implement as a third-party
>> package? If not, do more than ~80% of sites need this feature?" If the
>> answer to both questions is "no" (which is the case here, in my opinion),
>> then I don't favor including it in Django.
>>
>> For historic reasons we have some filters like phone2numeric which likely
>> don't meet this criteria. I don't see much benefit to deprecating them, but
>> let's not add more. Other opinions welcome.
>>
>>
>> On Monday, November 9, 2015 at 2:43:46 PM UTC-5, Paulo Maciel wrote:
>>>
>>> My proposal is to add a new template tag "age": {{ birthday|age }}.
>>> I think it is a common need for many users know the age from a date.
>>>
>>>
>>> --
>> 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 http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/d9ce1b89-1af0-4038-816f-24e13d25a666%40googlegroups.com
>> <https://groups.google.com/d/msgid/django-developers/d9ce1b89-1af0-4038-816f-24e13d25a666%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> 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/CAByqUgjS8nzfuwa_CApjAky-LTmADdukU9sKL3bLyh5ogA1oeA%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAByqUgjS8nzfuwa_CApjAky-LTmADdukU9sKL3bLyh5ogA1oeA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAMwjO1HHwU2d7Lngw0f4zQAt%3DOFEJmK%3DCC0TF8pXsXm2ixjobA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
