There would be an easy work arround I think. As django support and encourage custom django tags and filters in apps, you might want to copy the existing code of current working dicsort filter into your own app, rename it to something different than "dicsort" and use that renamed filter in your templates without being worried about the future breaking of builtin "dictsort" filter. This is what i typically do, whenever I need to customize an implementation of builtin features of django to meet my needs.
Still, I think the best place to get answer of this particular query was at issue tracker system of django, instead of this developers list, specially when the core developers are particularly busy with the upcoming release of django. Cheers Shihan On Jun 11, 2009, at 9:51 PM, Tom Evans <[email protected]> wrote: > > On Thu, 2009-06-11 at 11:30 -0400, Karen Tracey wrote: >> On Thu, Jun 11, 2009 at 11:07 AM, Tom Evans >> <[email protected]> >> wrote: >> >> >> >> I appreciate that; I'm asking if this undocumented feature is >> expected >> to work for the foreseeable future, and not likely to be >> changed in the >> future development of django. This, in my mind, is pertinent >> to >> django-developers. >> >> Cheers >> >> Tom >> >> PS, this is hardly a difficult question, could you not have >> simply >> answered it instead of being brusque? >> >> >> Hardly a difficult question? By your own phrasing you are asking >> about whether apparently undocumented behavior is likely to change in >> the future -- that doesn't strike me as a particularly easy question. >> If I were to try to come up with an answer I'd have to look at the >> history of the code in question -- is it an area of code that has >> been >> changed a lot in the past, how stable is it lately, how many open >> tickets are there at the moment that might be likely to hit it? How >> subtle is this undocumented effect -- is it something that a >> relatively minor change might cause a change in behavior or is it >> pretty well guaranteed by something fundamental in the way the code >> is >> presently implemented? Etc. >> >> I have no idea what the answer to this question is. All the >> information needed to answer those questions that I would look into >> to >> try to come up with an answer, though, is freely available in the svn >> history of the code and in trac. So you are as likely as anyone >> (barring someone who knows offhand, which isn't likely given no >> answer >> on -users) to be able to come up with a reasonably accurate answer. >> >> Karen >> > > Thanks, that actually *is* the answer: undocumented feature, do not > expect it to work in the long term. > I will come up with a different way to manage it - all I am trying > to do > is write manageable code that doesn't require my knowledge to > maintain. > > Cheers > > Tom > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
