On Sat, Feb 26, 2011 at 4:47 AM, Paul McMillan <[email protected]> wrote:
> Ticket #3094 needs a decision. > http://code.djangoproject.com/ticket/3094#comment:17 > > The quick summary: > > Once upon a time the XMLField accepted a schema and validated > documents against that. This hasn't been true since oldforms, yet the > documentation continues to proclaim this. Now, XMLField is basically a > TextField that takes an extra path argument. It's useless, and doesn't > validate anything. > > We need to either deprecate it, provide some validation, or fix the > docs to say it doesn't do anything. We can't fix the docs till we have > a decision on this ticket. > > Please weight in here or on the ticket. I'll write the patch for > whatever gets chosen. > > Thanks, > -Paul > > -- > 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. > > I'd favor having the field do nothing, emit a warning, and eventually be scrapped. It's adding nothing ATM and no one is crying. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -- 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.
