I've attached a patch per the discussion here. It's ready for review
and hopefully a speedy commit.
http://code.djangoproject.com/ticket/3094#comment:19
-Paul
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
On Sun, Feb 27, 2011 at 3:31 AM, Jacob Kaplan-Moss wrote:
> On Sat, Feb 26, 2011 at 11:47 AM, Paul McMillan wrote:
>> 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
On Sat, Feb 26, 2011 at 11:47 AM, Paul McMillan wrote:
> 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.
I say deprecate the field entirely. There isn't a
On Sat, Feb 26, 2011 at 4:47 AM, Paul McMillan 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
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