Opened 16 years ago
Closed 12 years ago
#10659 closed New feature (wontfix)
Properly handle Paste's MultiDict and UnicodeMultiDict in Django Form's SelectMultiple
Reported by: | amaslov | Owned by: | nobody |
---|---|---|---|
Component: | Forms | Version: | 1.0 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
We are using Django Forms with Pylons and improper handling of Paste's MultiDict objects in SelectMultiple.value_from_datadict is quite inconvenient. The fix is trivial - see the attached diff. Please add this to the trunk if possible.
Thanks!
Attachments (1)
Change History (7)
by , 16 years ago
Attachment: | widgets.diff added |
---|
comment:1 by , 16 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 16 years ago
I think I understand the issue from your point of view. I guess the simplest way to resolve this would be to apply the patch and if somebody else comes up with the 3rd dictionary type to support - add an abstraction. Since I have been the first one to require this functionality since the beginning - there's a great chance there will be no more such weirdos :).
comment:3 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:6 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
After 4 years I assume that anyone who needed this wrote a wrapper to handle the conversion...
This is a tricky one: I want to be able to support Paste here, but at the same time we can't possibly support every derivation of a dict that might get passed down into that function.