Opened 15 years ago

Closed 11 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)

widgets.diff (591 bytes ) - added by amaslov 15 years ago.

Download all attachments as: .zip

Change History (7)

by amaslov, 15 years ago

Attachment: widgets.diff added

comment:1 by Jacob, 15 years ago

Triage Stage: UnreviewedDesign decision needed

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.

comment:2 by amaslov, 15 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 Seth Buntin, 13 years ago

Severity: Normal
Type: New feature

comment:4 by Aymeric Augustin, 12 years ago

UI/UX: unset

Change UI/UX from NULL to False.

comment:5 by Aymeric Augustin, 12 years ago

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:6 by Aymeric Augustin, 11 years ago

Resolution: wontfix
Status: newclosed

After 4 years I assume that anyone who needed this wrote a wrapper to handle the conversion...

Note: See TracTickets for help on using tickets.
Back to Top