#3094: XMLField not being validated.
------------------------------------------------------+---------------------
Reporter: goliath.mailinglist@… | Owner: PaulM
Status: new | Milestone: 1.3
Component: Validators | Version: SVN
Resolution: | Keywords: relaxng
validator
Triage Stage: Accepted | Has patch: 0
Needs documentation: 1 | Needs tests: 0
Patch needs improvement: 0 |
------------------------------------------------------+---------------------
Changes (by PaulM):
* owner: jacob => PaulM
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* milestone: => 1.3
Comment:
I'd like to clear this wart up one way or another before 1.3.
Django is unlikely to bundle an external XML validator any time in the
near future.
There are a couple of options (in my order of preference):
1. Re-position it as a lightly validated convenience field named as a
reminder of the purpose. Implement the suggestion in #11474 and use
`xml.parsers.expat` to make sure that the XML is at least reasonably well
formed. Let users do any further schema validation themselves.
1. Deprecate it. Fix the docs to say it does nothing, and remove it as
expediently as possible.
1. Treat it as a documentation problem. Fix the docs to say it does
nothing special, and leave it alone.
Note: If we start validating entries to this field (which has been
unvalidated for at least 2 years), we will technically be introducing a
minor backwards incompatibility.
I'm assigning this ticket to myself because I am going to push to get one
of these options selected in time for 1.3.
--
Ticket URL: <http://code.djangoproject.com/ticket/3094#comment:17>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
