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