> But we're not talking about 'extensions of framework code' here. We're > talking about a custom tag, which is using an explicit piece of > functionality already provided by the framework: the ability to write > your own tags.
We started this thread from the bug in ifequal. But now we are talking that django missing important tag - ifless. Which should be built-in. > This is no more extending the code than is writing your > own views, and I'm sure you won't claim that Django should provide all > possible views so that you would only have to write your own if it's > really necessary. tags and views are on totally different level. It's like brick and building. Django developers supply bricks and I'm building buildings. It's ok if you have 1 project and you supporting 1 project for 5 years then you can write custom tag. But if you have 20 and you want to update them because django moved from 1.0 to 2.0, and then to 3.0. So functional which was deprecated are not more available. Then you have to patch all 20... Everybody should avoid custom tags unless you can't build application without them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
