Ian Bicking wrote: > You can't get unicode even via **params. Encoded strings work > okay, though.
Duh... I didn't even think about this. That being said, I still think that this is a largely irrelevant issue, as the developer can ensure that they use ascii parameter names. > If you use request.params.mixed() to get the keyword arguments, > you'll get lists in these cases. Some people find that > frustrating, as things may be lists or not (e.g., one checkbox > checked is not a list, two are), or misformed submissions cause > TypeErrors and whatnot when you unexpectedly get multiple > values. Anyway, that's the justification (along with ordering > and some other things) for not using a plain dict as the form > representation. This is precisely what I am doing right now, and it doesn't bother me at all that some things come across as lists. Its just a matter of a single `isinstance(value, list)`, which I can totally live with. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
