It's not... if you got control over the code. However my patch is specifically targeted at GET processing. You have to add a bunch of checks after each other, it quickly becomes overwhelming.
Alex, I'm interested by what you mean exactly by "tying __in to an arbitrary serialization format". What else would you propose? J. Leclanche / Adys On Tue, Oct 27, 2009 at 6:08 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > > On Tue, Oct 27, 2009 at 10:57 AM, Jerome Leclanche <adys...@gmail.com> wrote: >> I've got a patch to let __in accept comma-separated strings; I'm using >> this locally to avoid going through the trouble of splitting a string >> before processing a GET. > > I'm -1 on this. Is `filter(foo__in=s.split())` really all that hard? > > Jacob > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
