On Mon, Aug 18, 2008 at 11:05 PM, zdmytriv <[EMAIL PROTECTED]> wrote: > >> That's one good reason why it's not needed in core. If you need it and >> you understand the trade-offs and consequences, you can implement it >> immediately with no break in the flow. Django's supported third-party >> template tags since day 1 (and even earlier). :-) > > It's always bad idea to extend somebodies tool because when you wanted > to update current version with latest you can be in trouble. Latest > doesn't always support previous. > i.e. Django 1.0 uses Variable class to process variable from template > but 0.96 uses plain function resolve_variable() which is deprecated in > 1.0.
Changes like this one can hardly be the reason for your complaints. If you had written an ifless template tag yourself (which took 3 minutes to write) you'd maybe need 2 minutes more after a year fixing it for current trunk. I'd say compared to other work that is necessary to keep websites up-to-date. This stuff will not go into Django before 1.0, and there were no good points raised in this thread why it should go in after that. You don't need to extend core just to get these template tags -- you don't even need to write them yourself or keep them up-to-date, since somebody else is already doing this: http://code.google.com/p/django-template-utils/ See the comparison templatetag library. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
