On Wed, Dec 30, 2009 at 3:29 PM, Alex Gaynor <alex.gay...@gmail.com> wrote:
> The video I linked earlier had a critical point that I think a lot of > people are missing, adding a single filter may not add a lot to the > developer's burden directly but it impacts the perceptions (and > realities) of what kinds of things are reasonable for inclusion in > core. No one's ignoring that. But the truncate filter, specifically, isn't breaking new ground in terms of included filters. There's *already* a truncatewords filter. Adding this will not meaningfully impact the perceptions of core. -- dz -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
