Proposal: add new template tag "age"

[Paulo Maciel]

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.

[Tim Graham]

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.

[Dheerendra Rathor]

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). 

--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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.
For more options, visit https://groups.google.com/d/optout.

[Marc Tamlyn]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAByqUgjS8nzfuwa_CApjAky-LTmADdukU9sKL3bLyh5ogA1oeA%40mail.gmail.com.

[Jamie Norrish]

On Tue, 2015-11-10 at 18:50 +0000, Marc Tamlyn wrote:

> 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!

Further, age (for people, at least) is measured in different ways
around the world. See for example https://en.wikipedia.org/wiki/East_As
ian_age_reckoning

Jamie

[Collin Anderson]

Also, doing this from the backend seems like sub-par way to do it. I would recommend implementing this in javascript, so it can auto-update over time if you leave the window open.

[Tim Chase]

On 2015-11-11 14:44, Collin Anderson wrote:
> Also, doing this from the backend seems like sub-par way to do it.
> I would recommend implementing this in javascript, so it can
> auto-update over time if you leave the window open.

It shouldn't be limited to one or the other: doing it on the
back-end will allow it to correctly reflect the age as of the time
the request was made (and thus be available where JS is
unavailable/disabled). That field can then be updated client-side
with JS if it's available.

-tkc