#20684: Support form element attributes with no value
------------------------------+------------------------------------
Reporter: sneethling@… | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
------------------------------+------------------------------------
Comment (by anonymous):
Having slept about it,
(a) I concede that the implicit conversion should not be encouraged, and
(b) I agree that a special marker would be, essentially, interface cruft
that we would keep just for the benefit of something we don't really want.
But backwards compatibility still is a problem; I suggest to solve it with
a deprecation cycle. Given (a) above, I think even an expedited cycle may
be enough.
So,
Django 1.7:
`{'attr':True}` becomes `attr="True"`, with `DeprecationWarning('The
meaning of Boolean values for widget attributes will change in Django
1.8')`
Django 1.8:
`{'attr':True}` becomes `attr`
What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/20684#comment:16>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/080.aabb8860d997def5930accb2741f74f3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
